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

Annotations already cover read-only, idempotent, non-destructive and closed-world, yet the description adds real behavior: results come back in fixed bank order, capped at 10, and the response reports the total match count even when it is zero. It also enumerates the per-result payload (one-line description, why-line, buying note, budget band, photo link, deep link), which removes any ambiguity about what a call yields.

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 sentences, front-loaded with the core operation and followed by the return contract; nearly every clause carries information. The opening tagline 'Picked for them, not the store:' is the one piece of framing that does not earn its space against an otherwise dense, functional description.

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 five optional parameters, no required inputs, no output schema and annotations already stating the safety profile, the description supplies exactly the missing pieces: the data source size, result ordering and cap, and the shape and count semantics of the response. An agent has everything needed to call this correctly and interpret the output.

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%, so every parameter including the budget bands, recipient set and interest list is already documented in structured form, making 3 the baseline. The description only adds the combinability hint ('by interest, by keyword, or by both') and the general filter framing, without going beyond the schema on limit or budget semantics.

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 gives a specific verb and resource — 'searches the fixed bank of 255 gift ideas' — plus the search axes (interest, keyword, both) and filter dimensions, so the scope is unambiguous. It never names the siblings get_gift or pick_gift, so the boundary between 'search many' and 'fetch/choose one' is left for the agent to infer from the names.

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?

'by interest, by keyword, or by both' implies the main usage modes, and the recipient/budget filters hint at narrowing use cases. However there is no explicit when-to-use guidance, no statement of when to prefer get_gift or pick_gift instead, and no prerequisites or exclusions.

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