find_gift_card

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and openWorldHint. The description adds only returned fields, which are already represented by the output schema, and says nothing about not-found behavior, permissions, or matching rules.

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 a single compact sentence with no filler. The resource and identifier are front-loaded, and every phrase corresponds to useful information.

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 simple one-parameter lookup with rich annotations and an output schema, most invocation details are covered structurally. The description still lacks guidance on choosing between this and list_gift_cards and does not explain card-number format or not-found behavior.

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 burden for the single parameter. 'By number' maps the card_number parameter to an exact card identifier, but it does not specify format or matching behavior.

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 identifies the resource (gift card) and the lookup key (card number), and notes returned fields (balance, status, transactions). It is clear, but it does not explicitly distinguish this single-card lookup from the sibling list_gift_cards tool.

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 phrase 'by number' implies this is for looking up a specific gift card when the card number is known, which is a useful usage cue. However, there is no explicit when-to-use guidance, no exclusions, and no direct comparison to list_gift_cards.

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