List gift cards

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds pagination and filter behavior, but these are also documented in the schema. It does not cover response format or edge cases, but the tool is simple enough that this is not a major gap.

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, front-loaded sentence that states the action, resource, and key features without any filler or repetition. Every word earns its place.

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 list tool with full schema coverage and a readOnly annotation, the description is sufficient. It conveys the core purpose and mentions pagination and filters. The lack of an output schema is mitigated by the obvious return type, and the auto-pagination 'all' parameter is documented in the schema, so no critical information is missing.

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%, so the schema already explains all parameters. The description mentions 'status and purchase-date filters' but adds no new meaning beyond the schema. Baseline 3 is appropriate when the schema carries the full parameter documentation load.

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 action ('List'), resource ('gift cards'), and scope ('of the store'), with explicit mention of pagination and optional filters. This distinguishes it from get_gift_card (single) and other list tools.

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 description implies usage as a paginated list operation but provides no explicit when-to-use or alternative guidance (e.g., using get_gift_card for a single card). No exclusions are given, but the context is clear enough for a routine list tool.

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