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

The description frames the call as read-only diagnosis ('diagnosis only', 'Does NOT trigger a restart'), but the annotations declare readOnlyHint=false and destructiveHint=true, so the safety profile an agent relies on is contradicted. Although the description usefully enumerates the returned payload and the negative scope, the direct conflict with the structured safety hints forces the floor score.

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 purpose, then output content, then scope restriction. Every sentence carries distinct information with no filler.

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 the work of describing the return (failure classification, suggested next strategy, per-metric breakdown), and parameters are fully covered by the schema. The residual gap is side-effect/permission behavior, which the contradictory annotations leave ambiguous.

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, and the schema already documents both processId and the superadmin-only customerId. The description adds nothing about parameter meaning or format, so the baseline 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?

States a specific verb and resource with the triggering condition: 'Diagnose why an optimization failed to produce a winner.' The closing 'Does NOT trigger a restart — diagnosis only' separates it from mutation siblings such as trigger_optimization, optimize_model, and fix_worst_run without requiring a schema read.

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?

Gives a clear triggering context (an optimization that produced no winner) and one explicit exclusion (it does not restart the optimization). It stops short of naming the alternative tools an agent should reach for when it wants details, run-level diagnosis, or an actual re-run.

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