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

Annotations already establish that this is a safe, read-only, idempotent lookup. The description adds useful behavioral context by specifying that it returns up to 5 picks from guides and shows price bands rather than current prices. It does not cover pagination or failure behavior, but for this read-only tool that is a minor 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 three compact sentences, front-loads the usage condition, then explains the return shape and the price-band caveat. Every sentence contributes information an agent needs to select or interpret the tool.

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?

Because there is no output schema, the description appropriately explains the returned fields and the fact that results use price bands rather than live prices. Combined with complete parameter documentation and read-only annotations, it gives enough context to invoke and interpret the tool correctly.

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 input schema already documents budget_band, recipient, and limit thoroughly. The description reinforces budget and recipient filtering and the five-pick cap, but adds little parameter syntax or meaning beyond the schema itself.

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 states a specific verb and resource: finding gift picks for a budget and recipient. It also clarifies that results come from Corporate Gift Picks guides and include item name, price band, reason, and guide link. It does not explicitly distinguish itself from list_gift_guides or estimate_gift_budget, so it stops short of a 5.

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 gives a clear usage trigger: use when someone wants gift ideas for a given budget and recipient, with recipient examples. It does not explicitly state when to choose estimate_gift_budget or list_gift_guides instead, so the alternative-routing guidance is incomplete.

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