wordpress_delete_category

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

With no annotations provided, the description carries full burden. It discloses the critical behavioral trait that posts can be reassigned rather than deleted, but fails to explain the mechanism (e.g., whether reassignment is automatic to default category or controlled by the 'force' parameter).

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?

Two sentences with efficient information density, but the '[UNIFIED]' prefix wastes space without adding semantic value. The reassignment information is appropriately placed to clarify the deletion behavior.

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 output schema and zero schema description coverage, the description is incomplete. It fails to explain what the 'force' parameter actually controls, what happens to posts when 'force' is false/null, or what the 'site' parameter expects.

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 has 0% description coverage, yet the description provides no parameter explanations. It mentions 'reassign posts to another category' implying a target category parameter that doesn't exist in the schema, creating confusion about how reassignment is specified.

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?

States specific verb ('Delete') and resource ('WordPress category'). The mention of reassigning posts distinguishes it from simpler deletion tools. The '[UNIFIED]' prefix is implementation noise but doesn't obscure the core purpose.

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?

Describes behavioral capabilities ('permanently delete or reassign') but provides no explicit guidance on when to use this tool versus alternatives like wordpress_delete_tag, or when to choose reassignment over deletion.

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