mcp_delete_cpt_post

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

The description merely states the action without disclosing behavioral details like what happens to associated data, whether the force parameter affects behavior, or any side effects. With no annotations provided, the description should compensate but fails to do so, offering only a high-level summary.

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, concise sentence that efficiently communicates the core purpose. It avoids unnecessary words and is front-loaded with the action, which is beneficial for quick parsing.

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 the three parameters, lack of output schema, and no annotations, the description is too minimal. It does not explain the return value, side effects, or how this tool fits into the larger ecosystem of post deletion tools (e.g., wp_delete_post), leaving gaps in understanding for the agent.

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?

The input schema provides 100% description coverage for all parameters. The tool description does not add any further meaning beyond what the schema already states, so the baseline score of 3 is appropriate.

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 (delete) and the resource (custom post type post), making the tool's purpose immediately understandable. It does not, however, differentiate from sibling tools like mcp_delete_media or mcp_delete_menu, though the name itself suggests the specific resource type.

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 provided on when to use this tool versus alternatives, such as wp_delete_post or mcp_delete_media. There is no mention of prerequisites, contexts, or when deletion is appropriate, leaving the agent without direction.

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