verified__verify_receipts

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

No annotations are provided, so the description must carry the burden. It states the tool recomputes a hash chain and fee ledger, suggesting a read-only verification, but does not disclose side effects, authentication requirements, or error 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 two sentences and a bracketed tagline. The tagline is promotional but short. The core behavior is stated concisely, though the tagline could be removed to improve clarity.

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 and no annotations, the description lacks details on return values, error conditions, or prerequisites. For a single-parameter tool, the description does not fully equip an agent to use 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?

The only parameter 'service_id' has 0% schema description coverage and the tool description does not add any meaning beyond the name. The agent must infer its purpose (identifying the service) from context.

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 the tool 'recompute[s] a service's full receipt hash chain and fee ledger', giving a specific verb and resource. It distinguishes from siblings like 'get_receipt' (which retrieves individual receipts) and 'list_services' (which lists services).

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 mentions 'Any party can audit' implying use for auditing, but does not explicitly state when to use or not use this tool, nor does it compare to alternatives like 'get_receipt' for retrieval of specific receipts.

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