reveal_card

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

Discloses key behaviors: short-lived, single-use, bypasses PCI. However, with no annotations, additional details about authentication requirements or rate limits would be beneficial. No contradiction with annotations.

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?

Only two sentences, no redundant information. The purpose is front-loaded, and every word adds value.

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 the single parameter and no output schema, the description covers purpose, security context, and constraints thoroughly. No obvious gaps for this simple tool.

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 100% with a clear description for 'card_id'. The tool description does not add further semantic meaning beyond what the schema provides, so it meets the baseline.

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 clearly states the verb 'mint' and the resource 'one-time hosted link' with specific details (PAN/CVV). It explicitly distinguishes this tool from siblings like 'freeze_card' or 'get_card' by focusing on sensitive data disclosure and one-time use.

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?

Provides context about PCI compliance and limited lifespan, indicating when to use (to show card details to end users without handling them). Does not explicitly state when not to use or mention alternative tools, though context is clear enough.

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