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

With no annotations provided, the description carries the full burden. It does disclose that the tool is public and requires no pass, which is useful access context, but says nothing about whether it is read-only, what happens on an unknown hash, or the return shape. Partial coverage of the behavioral surface.

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 that front-loads the resource identity, with no filler. Slightly overloaded but appropriately sized for the tool's complexity.

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 one-parameter read tool with no output schema, the essentials are mostly present: access model and accepted hash types. Missing is any pointer to how it relates to the near-duplicate siblings ('receipt', 'verify_receipt') and any hint of the returned receipt shape.

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%, so the description must compensate for the single undocumented 'hash' parameter. It does enumerate the accepted forms (0x transaction hash, Nano send block hash, Solana transaction signature), which is genuinely useful, but the linkage to the 'hash' parameter is implicit and no format/validation guidance is given.

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 names the resource ('admission receipt for a payment') and details what it binds, but never states the verb/operation (retrieve? look up?) and gives no differentiation from close siblings like 'receipt' and 'verify_receipt'. An agent can infer it is a lookup keyed by hash, but the intent 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?

'Public; needs no pass' clarifies the authorization context, but there is no guidance on when to use this versus the 'receipt' or 'verify_receipt' siblings, nor any prerequisite or exclusion. Usage is left entirely to inference.

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