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

The description adds behavioral context beyond the annotations by describing deterministic comparison, material-difference reporting, caller-supplied verification rules, and the paid price. The readOnly, idempotent, and non-destructive hints are consistent with this read-and-compare behavior.

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?

The description is concise and front-loaded with the core behavior, followed by domain exclusions and cost. The phrase 'Intended for outcome assurance / cannot select' is slightly cryptic, but the overall structure is efficient and no sentence is wasted.

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, no parameter descriptions, and five parameters to clarify, the description is incomplete for an agent that must invoke the tool correctly. It does not describe the return format, how verification rules map to the optional parameters, or how material differences are represented.

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 0%, so the description must compensate, but it only generically mentions expected and observed values and 'caller-supplied verification rules.' It does not explain ignore_paths, required_paths, or numeric_tolerance, leaving their meaning and expected syntax undocumented.

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 clearly states that the tool compares caller-supplied expected and observed values and reports material differences, so the purpose is specific and actionable. However, it does not distinguish this tool from the nearly identically named sibling outcome_assurance_verification_07390ac9 or other verification tools, so it lacks explicit sibling differentiation.

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 description gives an explicit intended context ('Intended for outcome assurance / cannot select') and explicit exclusions ('Do not use for legal, identity, sanctions, fraud, contractual, or regulatory adjudication'). It does not name an alternative tool to use instead, which prevents a perfect score.

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