wordpress_delete_category

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 states 'Delete a category' but doesn't explain critical behaviors: whether deletion is permanent or reversible, what happens to posts in that category (e.g., reassignment or deletion), authentication requirements, or error conditions. This is inadequate for a destructive operation with zero annotation coverage.

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 extremely concise at three words, front-loading the core action without unnecessary elaboration. It wastes no space, though this brevity contributes to gaps in other dimensions. For a simple tool name, this minimalism is structurally efficient.

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 tool's complexity (a destructive operation with 2 parameters), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It fails to address behavioral risks, parameter meanings, or expected outcomes, making it insufficient for safe and effective use by an AI 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 description provides no information about parameters. With schema description coverage at 0% and two required parameters (categoryId and force), the schema alone gives only types (number, boolean). The description doesn't explain what categoryId refers to (e.g., ID from WordPress), what force does (e.g., delete even if category has posts), or provide examples, leaving semantics unclear.

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 resource ('a category'), making the purpose immediately understandable. It distinguishes from siblings like 'wordpress_update_category' or 'wordpress_get_categories' by specifying deletion, though it doesn't explicitly contrast with other deletion tools like 'wordpress_delete_term' which might handle similar resources.

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. For example, it doesn't mention prerequisites (e.g., needing admin permissions), when deletion is appropriate (e.g., vs. updating), or how it relates to siblings like 'wordpress_delete_term' for taxonomy terms. The description lacks context for decision-making.

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