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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds valuable context beyond that: the deletion takes effect on the phone's next sync, which is a non-obvious behavioral trait. This helps set expectations about the timing of the effect, so the description adds meaningful behavioral detail.

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 with a useful parenthetical explanation. Every word adds value, and the core action is front-loaded. There is no redundancy.

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 destructive action with one parameter and an output schema present, the description covers the key behavioral nuance (sync timing). It does not explain error cases or undo possibilities, but destructiveHint already signals permanence, and the output schema likely covers return values. Overall it is adequately complete for the tool's complexity.

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 coverage is 0%, so the description carries the burden of explaining parameters, but it does not mention 'id' at all. The parameter name alone suggests it is the identifier of the parse rule, but the description neither confirms this nor advises how to obtain a valid id. Given the low schema coverage, this is a notable gap.

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 specific action ('Remove one of your parse rules') and the resource (parse rules). This distinguishes it from sibling tools like save_parse_rule, test_parse_rule, and list_parse_rules, which clearly serve different purposes.

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?

Usage is implied: use this to delete a parse rule. However, the description does not explicitly mention alternatives or prerequisites (e.g., finding the rule ID via list_parse_rules, or conditions that must hold before deletion). The context signals suggest there are no true alternatives for this action, but the description could still guide when not to use it.

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