wordpress_delete_category

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

With no annotations, the description must disclose behavioral traits. It only states it deletes a category, but does not mention effects on associated posts, reversibility, or the role of the 'force' parameter. The agent lacks information about the operation's implications.

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. It is appropriately short and front-loaded, with no unnecessary words. However, it could be slightly expanded to include parameter details without losing conciseness.

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 has 2 required parameters and no output schema, the description is incomplete. It fails to explain the purpose of the 'force' parameter, any side effects, or the relationship to sibling tools. More context is needed for correct invocation.

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 0%, so the description should compensate. However, it does not describe the 'categoryId' or 'force' parameters, leaving the agent to infer meaning from parameter names alone. The description adds no semantic value beyond the schema.

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 'Delete a category' clearly states the verb (delete) and resource (category). It distinguishes from sibling tools like wordpress_delete_tag and wordpress_delete_term, as 'category' is a specific taxonomy. However, it does not add any extra context such as 'by ID' to clarify the required parameter.

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 like wordpress_update_category or wordpress_delete_term. The description does not mention prerequisites, when not to use, or scenarios where other tools would be more appropriate.

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