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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. Beyond that the description adds only the identity claim ("alias of search_gifts") and a parameter reminder — nothing about what a call actually returns (curated ASIN /dp links vs. marketplace search deep-links), which the schema hints at but the description never surfaces.

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 short sentences, front-loaded with the identity and purpose, with the critical marketplace/locale constraint called out in caps. No filler, though the reminder duplicates what the required-array already enforces.

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?

A 7-parameter tool with four undocumented enum/optional params (occasion, styleTag, budgetBand, limit), no output schema, and only an alias reference as behavioral context. An agent could not tell what differentiates the gift-suggestion output or how the optional filters change it.

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 only 43% across 7 parameters with 3 enums. The description only reminds the agent to pass marketplace and locale (both already marked required) and says nothing about q, limit, occasion, styleTag, or budgetBand, so it fails to compensate for the coverage gap.

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 (suggest Mother's Day gift ideas for a query) and explicitly names the sibling it mirrors ("Alias of search_gifts"), so an agent can place it relative to search_gifts. It stops short of saying how it differs from that sibling, which keeps it from 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?

"for a query on the user's marketplace" plus the Mother's Day framing implies when to reach for it, and "ALWAYS pass marketplace + locale" gives a hard usage constraint. But calling itself an alias of search_gifts with no when-to-prefer-either guidance leaves the agent to guess which of the two to call.

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