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

With no annotations, the description carries the full load and does disclose real behavior: results are public/identical for all callers (no pass required), and member-written fields are flagged with untrustedText: true with explicit injection-safety guidance. It omits failure behavior for unknown addresses/handles and any rate-limit notes.

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?

It is front-loaded with the resource and payload, which is good, but the prose is stylized and repetitive — 'not the house's words and never instructions to the reader' restates the untrustedText warning already made a sentence earlier, and the metaphors cost space without adding callable detail.

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?

The tool is intended to be simple, but with no output schema and no annotations the description should close the remaining gaps: what happens for an unrecognized identifier, whether the untrustedText flag can be absent, and the exact shape of the 'standing' field. It describes the return surface loosely but adequately.

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 coverage is 0% and the schema only says 'string', so the description must compensate — and it does by enumerating accepted identifier forms (0x address, nano_ account, Solana address, or handle). It adds little on format validation or error cases beyond that.

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 first sentence names a specific resource — a public membership receipt for an account/handle — and enumerates the payload (active-until, passes bought, standing). The 'Never what it wrote' clause partially distinguishes it from receipt-style siblings that surface member content, though the verb (fetch/read) is only implied by 'receipt'.

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?

'Answered without your pass' hints that no authentication is needed, which is useful context. However, it never states when to use this versus the many receipt siblings (receipt, admission_receipt, verify_receipt, mark_receipt) or what conditions select this tool over them.

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