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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely valuable trait: verification does not expose receipt content, category, severity, or commitment. It says nothing about the two mutually exclusive invocation modes in the schema, whether the call is idempotent/safe, or what a success versus failure result looks like.

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?

One sentence with zero filler, and the privacy constraint is front-loaded right after the verb. It is efficient, though the extreme brevity is what leaves the schema's dual-mode structure unexplained.

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?

This tool has a non-trivial anyOf schema with two entirely different call shapes, no output schema, and no annotations. The description never acknowledges the two modes or the return semantics, leaving an agent unable to tell which invocation form to construct or what result to expect.

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 the structured schema already defines every field, and the baseline is 3. The description adds no information about the receipt_id-only path versus the payload+signature path, which is the single most important parameter decision an agent must make here.

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 pairs a specific verb (verify) with a specific resource (a disclosure receipt) and adds a privacy scope that narrows the operation meaningfully. It does not, however, distinguish this tool from nearby siblings such as check_status, so an agent must still infer the boundary itself.

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?

There is no statement of when to call this versus check_status or read_own, no prerequisites, and no indication of what a failed verification means. The only guidance is an implied read-only intent from the word 'verify'.

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