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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that ('does not apply the change'). It adds real behavioral value beyond annotations: a five-minute token lifetime, an approval-scope requirement, and the side-effect note that already-processed invoice records remain. It does not describe what the preview payload contains.

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?

Three tight sentences, front-loaded with the action and its consequence, then the requirements and the non-application caveat. No filler, though the middle sentences could be ordered slightly better for scanning.

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 single-parameter, no-output-schema preview tool whose annotations already cover the safety profile, the description covers consequence, approval requirement, token lifetime, and non-mutation. The remaining gap is what the returned preview actually shows and how the token is supplied, but that is minor.

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?

Only one parameter (input.rule_id) with 0% schema description coverage, so the description must compensate and only partially does. 'Exact automation configuration rule' signals the argument is a specific rule identifier, but it omits the UUID format and where to obtain a rule_id (e.g., list_automation_rules), which the schema does not supply.

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?

States a specific verb and resource ('prepare permanently removing an exact automation configuration rule') and immediately clarifies it 'does not apply the change', which separates it from delete_automation_rule. The word 'exact' hints at a specific rule identity but the description never names the sibling delete tool explicitly.

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?

Implies a preview-then-confirm workflow by mentioning the five-minute confirmation token and 'requires approval-scope confirmation', which tells the agent this is a pre-flight step. It never explicitly says 'use this before delete_automation_rule' or names an alternative, so the routing guidance 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.