wp_delete_tag

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

With no annotations present, the description carries the full burden of disclosing behavioral traits. It does not state that the tool permanently destroys a tag, mention required permissions, or describe effects on associated posts. A deletion tool should clearly communicate its irrevocable nature.

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 sentence that merely repeats the tool's name in plain English. It is under-specified rather than concise, wasting the opportunity to add value. Every sentence should earn its place; this one does not.

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 simple deletion tool with two required parameters and no output schema, the description is incomplete. It omits essential context such as the need for a valid tag ID, the destructive nature, and any confirmation requirements, leaving significant gaps for agent understanding.

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 input schema has two required parameters (id and confirm) with 0% schema description coverage, yet the description provides no explanation of their meaning or usage. It fails to explain that 'id' is the tag ID and 'confirm' must be boolean true to proceed, leaving agents to guess.

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 WordPress tag' is essentially a tautology of the tool name 'wp_delete_tag', adding no new information. It does not specify any unique scope or behavior that distinguishes it from other deletion tools like wp_delete_category or wp_delete_post.

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 on when to use this tool versus alternatives (e.g., when to delete a tag vs. update or create). There is no mention of prerequisites, contexts, or the need for confirmation, leaving the agent without decision support.

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