Get Agent Receipt

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

Description adds context beyond annotations: confirms read-only and side-effect free, specifies tenant-bound Gateway GET, and clarifies scope boundaries for validity tiers.

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?

Front-loaded with purpose and usage, but the last sentence on validity tiers is somewhat extraneous for a tool description.

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?

Given one parameter with no schema docs and an output schema exists, description adequately covers the return type and use case, with clear boundaries.

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?

With 0% schema description coverage, the description explains that receipt_id is a SHA-256 action id or intent-terminal UUID, providing crucial format context absent from schema.

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?

Clearly states the tool retrieves a signed agent receipt JSON for a given receipt_id, with specific identifier types. Distinguishes from sibling tool for settlement receipts.

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?

Explicitly states when to use (need signed agent receipt for one receipt_id), when not to (settlement receipts), and provides alternative resource for agent-to-agent handoff.

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