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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read behavior is covered. The description adds useful context about 'pending or confirmed' statuses and machine-verifiability, but it does not disclose error conditions, authentication needs, or other behavioral traits beyond what annotations already provide.

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 one concise, front-loaded sentence with an active verb. It packs the operation, the resource, the statuses, and the lookup key without filler or redundancy.

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?

For a single-parameter read operation with an output schema and read-only annotations, the description is largely sufficient. The main gap is not addressing the relationship with get_reach_receipt or other siblings, which means an agent may need to do extra inference to confidently select the correct tool.

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 description gives a natural-language explanation that the single identifier can be a receipt or intent identifier, which complements the schema property name and regex pattern. However, it does not explain the difference between receipt and intent IDs, how status affects the lookup, or give examples; with 0% schema description coverage, this is only minimal compensation.

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 verb and resource: 'Read ... sponsorship proof by receipt or intent identifier.' It is clear about what the tool does and how it is invoked, but it does not explicitly distinguish itself from the similarly named sibling get_reach_receipt, so it does not fully earn a 5.

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 guidance about when to use get_receipt versus alternatives such as get_reach_receipt, and no when-not-to-use or prerequisite information. The only usage signal is the implied lookup-by-identifier workflow, which is not enough for good tool selection among the receipt-related siblings.

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