cf_delete_redirect

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

Annotations already indicate destructiveHint=true, so description does not need to reiterate. However, description adds important behavioral context: the gating by an environment variable (SEO_MCP_ALLOW_DESTRUCTIVE), which is not in annotations.

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?

Two concise sentences that deliver all critical information without unnecessary words. Front-loads the purpose and includes key usage context.

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 well-defined parameters and annotations, the description covers purpose, input source, and access control. No output schema is needed, and sibling tools provide relevant context.

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 already covers both parameters with good descriptions (100% coverage). The description adds value by clarifying that rule_id comes from the cf_list_redirects tool, aiding the agent in understanding the data flow.

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 clearly states the action ('Delete one single (dynamic) redirect rule'), the resource ('redirect rule'), and the identifier ('by its id'). It also distinguishes itself from cf_create_redirect as the rollback path.

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?

Explicitly explains when to use this tool (as the rollback path for cf_create_redirect) and where to obtain the required input ('Get the rule id from cf_list_redirects'). Also mentions the gating condition requiring SEO_MCP_ALLOW_DESTRUCTIVE=true.

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