wp_create_cpt_item

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool creates an item, without mentioning permissions, default status behavior, validation, duplicate handling, or any side effects, leaving significant behavioral uncertainty for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single clear sentence with no filler, but for a tool with 10 parameters and sparse schema documentation, this is under-specification rather than effective conciseness. It front-loads the core purpose but fails to carry the weight the definition needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters, no output schema, no annotations, and only 10% schema description coverage, a one-line high-level description is far from complete. An agent would still lack essential context about required inputs, behavior, defaults, and what the tool returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema description coverage is only 10%, and the tool description adds no parameter-level meaning. It does not explain the required post_type and title fields, the meta object, status options, or scheduled_date semantics beyond what property names or one schema description already provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (create) and the resource (an item in a custom post type), which aligns with the tool name. It is distinguishable from sibling tools like wp_create_post and wp_create_page via the 'custom post type' qualifier, though it does not explicitly name or contrast those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool versus alternatives such as wp_create_post, wp_create_page, or wp_create_taxonomy_term. The description only states what the tool does, with no context about prerequisites, exclusions, or preferred use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.