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

With no annotations, the description carries the full burden. It discloses a meaningful privacy behavior ('their data never leaves you') and implies a read-only list operation, but it does not mention other aspects like authentication, rate limits, or side effects. For a simple list tool, this is adequate but not exhaustive; the description adds some context beyond the obvious.

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 two concise sentences: the first states the action, the second provides actionable guidance and a privacy note. Every part earns its place with no fluff or redundancy.

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 parameterless tool with no output schema, the description adequately explains what the tool does and how to apply the results. It could explicitly mention that it returns a list of offers, but that is implied by 'List the gift-offer shelf.' The guidance on selection and privacy adds useful context.

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?

There are zero parameters, so the description cannot add parameter semantics. The baseline of 4 is appropriate because the schema already covers everything (trivially, since there are no inputs), and the description need not explain anything about inputs.

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 tool lists 'the gift-offer shelf', using a specific verb (list) and resource (gift offers), which distinguishes it from sibling tools like card templates or phrases. The additional instruction about selecting an offer reinforces its role in the gift-giving workflow, making the purpose unmistakable.

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?

It provides clear guidance on how to use the output (e.g., 'Pick the one offer... match on what you already know about them'), which tells the agent what to do with the results. It doesn't explicitly state when to use this tool versus alternatives, but the distinct resource type (offers) implicitly differentiates it from siblings. The privacy note also adds context on how to approach selection.

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