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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond those annotations by explaining that the receipt distinguishes transport acceptance from remote-content activity and by warning that tracking-pixel activity may come from a proxy or scanner rather than a human reader.

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 three tight sentences with the core action front-loaded. Each sentence contributes distinct value: the operation, the distinction between receipt types, and the important interpretation caveat.

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 no output schema, the description carries the burden of explaining what the receipt means, and it does so by contrasting transport acceptance with remote-content activity and warning against treating tracking pixels as proof of reading. It could be more complete by explaining how to obtain a dispatch_id or what fields the receipt returns.

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 carry the parameter semantics. It names dispatch_id but does not explain its format, where to obtain it, or what constitutes a valid value, leaving the 32-character hex pattern in the schema as the only constraint.

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 an owned dispatch receipt by dispatch_id. It also distinguishes the tool's scope from sibling tools like get_ecard and list_ecards by focusing on dispatch receipts, though it does not explicitly name the alternatives.

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?

The usage context is implied: use this when you need the status of a specific dispatch. However, there is no explicit guidance about when to choose this over get_ecard, search_ecards, or list_ecards, and no prerequisites or exclusions are stated.

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