wp_delete_term

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

The description thoroughly explains the consequences: permanent deletion, no trash, force is required, posts keep their content but lose the term, and the term's archive URL 404s. It also explicitly mentions the dry_run default and the allow_prod requirement, making the 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 text is slightly verbose with repeated warnings (e.g., 'DEFAULTS TO' in caps) but every sentence contributes relevant safety context. The structure is acceptable for a destructive operation, focusing on warnings and prerequisites.

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?

Despite lacking annotations and an output schema, the description gives comprehensive context: consequences, safety defaults, related tools (wp_list_terms, wp_set_post_terms), and reminders about production protection. This is sufficient for an agent to safely decide when and how to invoke the tool.

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 mentions that term_id comes from wp_list_terms and states the defaults for dry_run and allow_prod, but it does not explain the install or taxonomy parameters. Since the input schema has no descriptions and coverage is 0%, the description only partially compensates for the missing parameter semantics.

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 states clearly 'Delete a term' and emphasizes the permanent nature of the operation, distinguishing it from update or list operations. It also notes that the term is unassigned from every post, leaving no ambiguity about the tool's core function.

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?

It provides actionable guidance: check the term's post count with wp_list_terms first, prefer re-filing posts with wp_set_post_terms before deletion, and defaults to dry_run=true to avoid accidental deletion. This gives the agent a clear safe workflow.

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