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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description goes beyond them by disclosing what the response contains (remaining value, customer, status) and the underlying endpoint, which matters because there is no output schema. It omits lookup-failure behavior, but the value-add over annotations is real.

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?

One short sentence front-loads the resource and identifier before listing useful return fields, with the endpoint appended last. There is no filler, though the endpoint path is arguably redundant for an agent.

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 single-parameter read tool with annotations and no output schema, the description covers purpose, identifier, and the salient returned fields. Only edge behavior (not-found handling) and an explicit pointer to the list tool are 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% and the single parameter already documents that it accepts a "Gift card number or id." The description repeats that same dual-acceptance point plus the endpoint path, adding little beyond the structured field, so baseline 3 applies.

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?

"One gift card by its card number (or id)" names a specific verb and resource, and the word "one" plus the fields returned makes it distinguishable from phppos_list_gift_cards without opening the schema. It stops short of explicitly naming the sibling, so it is clear but not maximally differentiating.

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 singular retrieval is implied by "One gift card" and the required card number, which suggests use this when the identifier is known rather than for browsing. There is no explicit statement of when to prefer this over phppos_list_gift_cards or what to do if the number is unknown.

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