get_gift_cards

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

With no annotations, the description must disclose behavioral traits, but it only states 'Fetch gift cards' with no mention of read-only nature, pagination, filtering, or any side effects. The tool likely returns a list, but this is not stated, and no details on rate limits or auth are provided.

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 extremely concise, a single sentence of six words, and is easy to parse. However, it is almost too sparse, offering no additional context that could aid tool selection, making it efficient but minimal.

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?

Despite a well-documented schema, the description is incomplete for a tool with pagination and filtering capabilities. It does not mention that it returns a list of gift cards, that results can be paginated, or how it relates to the singular get_gift_card. With no output schema, the agent lacks information about the return value.

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?

The input schema provides 100% coverage with detailed descriptions for all five parameters, including pagination, filtering, sorting, and defaults. The description adds no parameter information beyond the schema, so the baseline score of 3 is appropriate.

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 'Fetch gift cards from the store' clearly states the action (fetch) and resource (gift cards), and the plural form distinguishes it from the singular get_gift_card sibling. It is concise and specific, though it does not explicitly mention that it supports listing/pagination.

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?

No guidance is provided on when to use this tool versus alternatives like get_gift_card or get_gift_card_transactions. The description gives no context about common use cases, prerequisites, or exclusions, leaving the agent to infer usage from the schema.

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