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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful behavior: it does not echo content, and it requires matching 64-hex expected/observed hashes. But it omits what counts as 'successful', what a mismatch returns, and the pricing/billing mechanics beyond the flat fee.

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 dense sentence followed by the price. Front-loaded with the core action and no filler. The dense clause stacking slightly hurts readability but nothing 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?

A paid, mutation-adjacent evidence tool with a nested 6-field object, 0% schema coverage, and no output schema. The description should explain the input object shape, the matching rule, mismatch behavior, and the return value. It covers only the hash-matching idea and the price, leaving most of what an agent needs to call it correctly unspecified.

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% and the single required 'delivery' parameter is a nested object with six required sub-fields, none documented. The description gestures at the fields (transaction, request, content hashes) but supplies no format, no max length enforcement, and no explanation of the hash-matching semantics the caller must satisfy.

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 verb ('Bind') and the resources involved (delivery, transaction, request, content hashes), which is more specific than a tautology. However 'Bind successful delivery' is jargon that doesn't clearly explain to an agent what the tool actually produces or how it differs from near siblings like transaction_assurance, agent_task_handoff_receipt, or attest. The purpose is inferred rather than stated plainly.

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?

No when-to-use guidance and no mention of alternatives, despite dozens of closely-named evidence/attestation siblings. The '0.003 USDC' price hints at a paid operation but the description never says when this paid call is warranted versus free siblings like schema_normalize_free or try_service.

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