wp_delete_redirect

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

With no annotations, the description 'Delete a redirect' implies a destructive action but offers no details on reversibility, permissions, or side effects. The confirm parameter is not acknowledged, leaving the agent unaware of the safety mechanism.

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 very short but at the expense of completeness. It lacks any structure or front-loading of critical information, making it closer to underspecification than effective 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?

Given the absence of annotations and output schema, the description should fully explain the tool's behavior and parameters. It fails to do so, omitting the mandatory confirm parameter and any return value details.

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 fails to explain the 'id' and 'confirm' parameters. It provides no value beyond the schema itself, leaving the agent to guess their purpose and constraints.

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 redirect' clearly states the verb and resource, and distinguishes it from sibling tools like wp_delete_post or wp_delete_page. However, it lacks any additional context about the scope or specific redirect type.

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 usage guidance provided. The description does not mention when to use this tool over alternatives (e.g., wp_update_redirect or wp_list_redirects) or any prerequisites like needing the id or confirm parameter.

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