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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that the tool compares ALL variants and returns metrics plus content differences, which is useful context, but it discloses nothing about auth requirements (beyond the schema's customerId note), result size, or pagination.

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?

A single front-loaded sentence that immediately states the action and its output, with no filler. It is efficient though terse, and could have spent one more clause on differentiation.

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?

No output schema exists, so the description carries the return-value burden and does name the comparison output (metrics and content differences). Combined with annotations covering the safety profile and 100% schema coverage of the two parameters, an agent has enough to call it correctly.

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%, so both processId and the Converra-superadmin customerId are already documented in the schema. The description adds no parameter syntax or format detail beyond that, which matches the baseline of 3 when the schema does the heavy lifting.

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 ('Get detailed comparison of all variants from an optimization run') and names the returned scope (metrics and content differences). However, it does not explicitly distinguish itself from close siblings like get_optimization_details or validate_variant, so an agent must infer the boundary.

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 by 'from an optimization run', letting the agent know the processId must reference an optimization process. There is no explicit when-to-use, when-not-to-use, or named alternative among the many optimization-related siblings.

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