wordpress_delete_term

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action without elaborating on consequences such as irreversibility, the effect of the 'force' parameter, or cascading impacts on associated objects. It adds no behavioral context beyond the tool name's implied deletion.

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, efficiently worded sentence with no redundancy. It is front-loaded with the action and resource, but it is so brief that it misses opportunities to include essential information without sacrificing clarity.

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?

The tool is a destructive operation with no annotations, no output schema, and a required 'force' parameter that is unexplained. The description is far too sparse for an agent to safely execute the task, lacking critical context about the force flag and the term deletion's broader effects.

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%, and the description does not explain any parameters. The schema lists taxonomy, termId, and force, but the description fails to clarify the meaning of 'force' or how the parameters interact. With three required parameters and no description, parameter semantics are entirely undeveloped.

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 term from a taxonomy' uses a specific verb ('delete') and resource ('term'), clearly indicating the action and scope. It distinguishes from sibling tools like create_term, update_term, and get_terms by specifying deletion, and the 'taxonomy' context separates it from delete_category/delete_tag.

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 about when to use this tool versus alternatives such as delete_category or delete_tag. There is no mention of prerequisites, exclusions, or preferred scenarios, leaving the agent to infer usage solely from the action.

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