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

Annotations already carry readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context: determinism, reliance on caller-supplied verification rules, and the paid pricing ($0.002 USD per call). These traits are beyond the structured annotations and help an agent set expectations.

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 concise sentences front-load the core operation, then cover intended use, exclusions, and pricing. Every sentence adds information and there is no repetition of schema or annotation data.

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?

Given 0% schema coverage and no output schema, the agent lacks essential details: what 'material differences' means, how verification rules map to parameters, and what the response shape is. The domain and pricing are covered, but the operational mechanics are under-specified for a tool with five parameters.

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 explain the parameters. It only implicitly references expected and observed via the phrase 'expected and observed values' and hints at verification rules, but does not clarify ignore_paths, required_paths, or numeric_tolerance semantics. This is a significant gap for a 5-parameter tool.

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 states a specific action ('deterministically compares caller-supplied expected and observed values and reports material differences') on a clear resource. It also defines the intended domain (trust identity permission / execution risk) and explicitly lists off-limits purposes, helping an agent distinguish this verification tool from siblings.

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 provides a clear when-to-use context ('Intended for trust identity permission / execution risk') and explicit when-not-to-use domains ('Do not use for legal, identity, sanctions, fraud, contractual, or regulatory adjudication'). However, it does not name any alternative tool among the large sibling set.

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