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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description needn't restate them. It does contribute one thing annotations can't: the shape of the result (billing address and the labels paid for), which matters because there is no output schema—though it says nothing about formatting, not-found behavior, or error cases.

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 a single tight sentence with no waste, but it is a verbless fragment, so the reader gets resource semantics before ever learning what the tool does. Conciseness is fine; front-loading the action would be better.

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 with no output schema, the description partially covers the gap by describing returned content (billing address, paid labels). It still omits the action verb and any link to list_receipts, leaving the agent to reconstruct the lookup pattern from structured fields.

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 100% and receipt_id carries a pattern plus a pointer to list_receipts, so the schema does the work. The description contributes no additional meaning about the parameter, which is the correct baseline 3 when the schema is self-sufficient.

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 is a noun phrase that defines the resource (a payment to Pirate Ship plus its billing address and paid labels) but never states the retrieval verb, so an agent must infer it from the tool name. It adds useful semantic content beyond the title, but it does not differentiate from the sibling list_receipts, which the schema—not the description—points to.

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 on when to call this versus list_receipts or list_transactions, and no prerequisites or exclusions are stated. The only routing hint ('receipt_id from list_receipts') lives in the schema, not the description.

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