wp_delete_category

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

With no annotations, the description carries the full burden. 'Permanently' usefully discloses irreversibility and aligns with the schema's force: true. However, it omits other behavioral traits: what happens to posts in the deleted category, permission requirements, or that dry_run can preview the deletion safely.

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?

A single five-word sentence, front-loaded with the action and resource. No filler or redundant detail.

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?

For a destructive operation with no annotations and no output schema, this one-liner is insufficient. It leaves out critical safety context: side effects on posts, inability to delete the default category, and the dry_run preview option. The agent gets the core action but not enough to invoke it safely and correctly.

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?

Schema description coverage is only 33% (only dry_run has a description). The tool description adds no parameter meaning: it does not explain id or force. The force const:true is inferable from the schema, but the description should compensate for the low coverage and does not.

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 states a specific verb ('delete'), a clear resource ('WordPress category'), and a key qualifier ('Permanently'). This distinguishes it from sibling tools like wp_delete_tag, wp_delete_post, and wp_delete_page by naming the exact 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 given about when to use this tool versus alternatives. It does not mention wp_delete_tag for tags, nor does it warn about constraints like deleting the default category. The intended use is only implied by the name and description.

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