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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds value by explaining that it is a plain delete with no approval step and that rules are inert config, so deleting unfired config has no candidate movement. This goes beyond the annotations without contradicting them.

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 two sentences: the first states the core action, the second adds critical behavioral nuance. It is front-loaded, dense, and contains no filler. 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 simple delete tool with two parameters, the description covers the purpose and the safety aspect (no candidates moved for unfired config). However, it lacks parameter explanations, particularly request_id, and does not mention idempotency or error behavior, leaving the definition incomplete for a tool with zero schema descriptions and no output schema.

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%, so the description must compensate for parameter meaning. It does not mention rule_id or request_id at all. While rule_id is inferable from the resource name, request_id remains completely unexplained, leaving a significant gap for agents selecting or invoking the tool.

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 and resource: 'Delete a stage automation rule.' It distinguishes from sibling tools by explicitly noting 'Plain delete (no approval preview→bind)', separating it from the preview/bind pattern used elsewhere in the toolset.

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 context on when this tool is appropriate: it is the direct delete without an approval preview→bind flow, and it notes that rules are inert config so deleting unfired config moves no candidates. However, it does not explicitly mention alternatives or exclusions, like whether to use a different tool if you need to preview consequences.

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