Delete a term

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds valuable detail: 'Terms have no trash — deletion is immediate and permanent', the confirm:true requirement, and the side effect that content assignments are removed but content is not deleted, with fallback to default category. This enriches the agent's understanding beyond the annotation flags.

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 three sentences, front-loaded with the core action, followed by essential caveats. There is no redundant phrasing; every sentence earns its place.

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 delete with 4 parameters and no output schema, the description covers the critical behavioral aspects: permanence, confirm requirement, and content-assignment consequences. It does not specify return format or error handling, but those are less critical given the explicit caveats. Overall, it provides sufficient context for correct invocation.

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 coverage is 100% with each parameter described, so the baseline is 3. The description reinforces that confirm must be true ('requires confirm: true') but does not add new meaning to site_id or taxonomy beyond the schema. It adds minimal extra semantic value.

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 'Delete a term from any taxonomy' with a specific verb and resource, and the scope 'any taxonomy' clearly distinguishes it from get_term, create_term, update_term, and list_terms. It is unambiguous what the tool does and how it differs from term-related siblings.

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 no explicit guidance on when to use this tool versus alternatives (e.g., update_term for modifications) or when it should not be used (e.g., when only a soft removal is needed). The purpose is implied by the name, but no conditional or exclusionary context is given.

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