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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered, but the description adds nothing beyond that: no statement that deletion is permanent/irreversible, whether dependent rules or artifacts are affected, or what permissions are required. For a destructive mutation, this is a notable gap.

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?

A single front-loaded sentence with no padding, which is structurally clean, but it is bare to the point of under-specification for a destructive operation rather than optimally concise.

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?

An output schema exists so return values need not be explained, but for a destructive two-parameter tool the description omits the confirmation/irreversibility behavior, permission requirements, and the project_slug disambiguation that an agent needs before invoking it.

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 50%: project_slug is documented in the schema (including its single-project optionality), but rule_id has no description at all. The prose only obliquely implies 'a routing rule' and 'a project' and never clarifies the id format or the project scoping rule, so it fails to compensate for the uncovered parameter.

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 a specific verb and resource ("Delete a routing rule") and scopes it to a project, which cleanly separates it from routing_rules.create, routing_rules.update, and routing_rules.list. It stops short of any explicit sibling routing language, but the purpose is unambiguous.

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?

There is no guidance on when to use this versus routing_rules.update (e.g., disabling vs. removing) or any prerequisites such as ownership of the rule/project. The only usage hint is the implicit 'from a project' scoping, which is inferred rather than stated.

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