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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is partly covered; the description still adds real value by asserting it 'never redeems or changes the card' and by warning that the full code is echoed back and should not be repeated elsewhere. That data-handling caution is not derivable from annotations or schema.

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?

Two dense sentences: the first enumerates the payload, the second handles the sensitive-return warning and the read-only guarantee, and the route is appended last. Nothing is padded and the load-bearing content is front-loaded.

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?

With no output schema, the description usefully inventories the response (balance fields, status flags, expiry, recipient, order, fulfilment, event ledger), which is exactly what an agent needs to consume the result. It stops short of noting error behavior for an unknown code or how the ledger is ordered, but is otherwise complete for a single-resource read.

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 coverage is 100% with only two simple params (code, test_mode), so the schema carries the parameter burden. The description adds nothing about test_mode's test-vs-live data semantics or code format beyond what the schema states, which is the expected baseline-3 case.

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?

States a specific verb and resource ('one gift card by its code') and enumerates the returned facets (balance, status, expiry, recipient, order, fulfilment, ledger). The singular framing clearly distinguishes it from the sibling giftup_list_gift_cards, and the raw route GET /gift-cards/{code} pins the contract.

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?

Use is implied: you call this when you already hold a code, versus listing when you don't. There is no explicit when-not statement or named alternative, and no guidance on how to recover from an invalid/unknown code, so the guidance stays at the implied level.

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