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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety baseline is covered. The description adds genuinely useful non-obvious behavior: the operation is a no-op preview unless confirm is exactly true, and any non-true value degrades to preview. It omits whether the preview reports affected items or what permissions are needed.

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 short sentences with the destructive/preview caveat front-loaded right after the purpose; no filler. Slightly telegraphic, but every clause carries weight.

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 two-parameter destructive tool with annotations covering the safety profile and no output schema, the description supplies the critical behavioral fact (preview-by-default). The main remaining gap is that the preview result format is unstated, though the absence of an output schema makes that a moderate shortfall rather than a critical one.

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%: confirm is already fully documented in the schema, and the description essentially restates that same contract, while automationId remains unexplained in both places (no format, no hint on where to obtain it). With half the schema undocumented, the description does not compensate enough to exceed the baseline.

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 gives a specific verb+resource: 'Deletes a board rule,' which maps cleanly to delete_automation and distinguishes it from sibling deletions like delete_board, delete_task, or delete_list. It doesn't explicitly name or contrast with siblings such as set_automation_enabled (disable vs. delete), so it falls just short of a 5.

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 confirm/preview note implies a two-step usage pattern (preview first, then commit), which is real usage guidance. However, it never states when to delete an automation versus disabling it via set_automation_enabled, nor any prerequisites such as permission requirements. Usage is implied rather than stated.

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