wordpress_delete_category

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

The description claims the tool can reassign posts to another category, but the input schema lacks a parameter for the target category, creating ambiguity. No details on side effects, permissions, or reversibility are provided, and annotations are absent.

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 very short but includes a confusing '[UNIFIED]' prefix. It is not structured to separate purpose from usage details, though it remains brief.

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?

With three parameters, no output schema, and no annotations, the description is highly incomplete. Missing explanations of site, force, reassignment mechanics, and expected results.

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%, yet the description does not explain any parameter (site, force, category_id). The mention of reassignment is not mapped to a parameter, leaving the force parameter's meaning 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 tool deletes a WordPress category and mentions the two modes (permanent deletion or reassignment of posts), which distinguishes it from sibling tools like create_category, update_category, and list_categories.

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 (e.g., update_category for modifying a category, or other delete tools). Conditions for when reassignment occurs versus permanent deletion are not explicitly linked to the force parameter.

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