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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful output context (what the plan contains and how reductions are measured), but says nothing about auth, rate limits, or whether a scan must pre-exist beyond the terse 'Uses the latest scan on file' in the schema.

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?

It is a single sentence, front-loaded with the purpose, and no clause is pure filler. But it is an extremely dense run-on with stacked jargon that is hard to parse in one pass, which undercuts structure.

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?

With no output schema, the description does carry the burden of describing the return value and does so reasonably well (plan contents, per-step chain size, detector stop point). It is still missing prerequisites and any usage framing, which leaves gaps for a plan-generation tool in a large sibling family.

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 100% with only two parameters (id, domain), both already documented in the schema. The description adds no parameter-level meaning at all, so the baseline of 3 applies.

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 names the exact finding it targets (MACHINE_CHAIN_HEAVY) and the artifact it produces (a fix plan with measured reductions and the step at which the detector stops firing), which distinguishes it from sibling fix_* tools. However, it opens with a noun phrase rather than a verb, and the heavy jargon makes the core purpose take work to extract.

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?

Use is implied by the finding name MACHINE_CHAIN_HEAVY, so an agent with that finding can infer when to call it. There is no explicit when-to-use statement, no exclusion, and no routing to alternatives such as fix_robots or explain_finding despite a crowded fix_* sibling set.

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