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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds genuine value beyond them: the exact data scope ('only payment instructions and receipt status, never card details or donor personal information'), a security caveat about redirects/claims, and a privacy warning that invoice URLs disclose the wallet address. This is substantive behavioral context beyond the structured fields.

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?

Four short, front-loaded sentences that each carry distinct information (data scope, security caveat, privacy warning, auth). No filler, though the sentences are somewhat loosely sequenced rather than building on the core purpose.

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 an output schema present, return values need not be explained, and the annotations carry the safety profile. The description adequately covers data scope, security behavior, privacy, and auth for a simple read. The one gap is the lack of any explanation of the funding_id parameter, which is a moderate omission.

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 parameter funding_id carries only a pattern, no semantic explanation. The description never mentions funding_id at all, so it does not compensate for the coverage gap by explaining what the identifier is or where it comes from. With one undocumented parameter, the baseline-4 case for zero params does not apply.

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 title and description make clear this is a read that returns payment instructions and receipt status for a funding record, keyed by funding_id. It does not explicitly name the write sibling (claim_crypto_funding), but the mention that 'client claims cannot mark a payment paid' gestures toward the distinction between reading status and claiming. Clear purpose, but sibling differentiation is only implied.

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 a hint about when not to expect this to resolve payment ('Redirects and client claims cannot mark a payment paid'), which implicitly points to claim_crypto_funding, but no explicit when-to-use or when-not-to-use guidance. The 'Public; no authentication required' line gives context but not invocation guidance. Usage is implied rather than stated.

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