get_gift_card_transactions

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

With no annotations, the description must disclose behavioral traits. 'Fetch' implies a read-only operation, but the description does not mention that results are paginated (cursor 'after', 'first' limit) or what the response structure looks like. It essentially restates the tool name without adding meaningful behavioral context.

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, short sentence with no fluff or repetition. However, it is so minimal that it borders on under-specification; still, it is concise and front-loaded with the verb and resource.

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?

This is a list operation with pagination parameters, no output schema, and no annotations. The description fails to communicate that the tool returns a list/collection of transactions, that results are paginated, or any other context needed to understand its full behavior. The schema hints at pagination but the description does not reinforce or explain it.

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 of all three parameters with descriptions (giftCardId, after, first), so the description does not need to add parameter details. The description adds no extra semantics beyond the schema, securing the baseline score.

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 identifies the resource ('gift card transactions') and the action ('Fetch'), which distinguishes it from sibling tools that deal with gift cards themselves (e.g., get_gift_cards, credit_gift_card). However, it lacks any scope nuance (e.g., 'all transactions' or 'by gift card'), so it does not fully differentiate within the transactions domain.

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 offers no guidance on when to use this tool versus alternatives like get_gift_cards, get_gift_card, or credit_gift_card. There is no mention of typical use cases, prerequisites, or when not to use it.

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