wp_taxonomies_delete_category

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It states that trash is not available for terms, so deletion is always permanent, and it explicitly explains the impact on posts (they are not deleted but lose the category). It also discloses the confirm string requirement and MODE=full as environmental constraints, making the tool's behavior highly transparent.

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 exactly two sentences, with the core action and permanence in the first sentence, and prerequisites plus post-effects in the second. Every word adds value; there is no padding or repetition of schema fields. This is a model of 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?

For a destructive operation with no annotations or output schema, the description covers the essential context: permanence, confirm requirement, MODE=full requirement, and the effect on posts. It does not describe the response format or error cases, but these are less critical for a delete operation and the description is otherwise complete enough for an agent to use the tool 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 0%, so the description must compensate. It fully specifies the confirm parameter format ('DELETE_CATEGORY_<id>'), which is critical because otherwise confirm is just an undocumented string. The id parameter is implicitly the category ID from the tool name and its use in the confirm string. This adds meaningful semantics beyond the bare 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 begins with 'Delete a category,' a specific verb and resource that clearly distinguishes this from sibling tools like wp_taxonomies_delete_tag and wp_taxonomies_create_category. It also adds important context that the deletion is permanent, reinforcing the 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?

The description provides explicit prerequisites: the confirm parameter must be in the format 'DELETE_CATEGORY_<id>' and the operation requires MODE=full. It also clarifies that posts in the category are not deleted but only lose the assignment. However, it does not explicitly name alternatives or exclusions (e.g., 'use this instead of delete_tag'), so it falls short of a 5.

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