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

The description details dynamic behavior—specifically how output links are generated (ASIN links vs. search deep-links) based on the selected marketplace. This is critical context that goes beyond the simple readOnlyHint annotation.

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 information is highly concentrated, effectively merging pagination, scope, and operational constraints into a single dense paragraph without unnecessary filler.

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?

Given the need to explain complex output logic and mandatory constraints, the definition is robust. It provides sufficient guidance to understand how this curated catalog tool differs from general search functions.

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?

While schema coverage is moderate (56%), the description adds vital semantic context to the required `marketplace` parameter, explaining how the choice impacts the final output links (ASIN vs. search links).

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 immediately identifies the resource ('curated Valentine gift starters') and distinguishes itself from the primary discovery mechanism ('search_gifts') and the search sibling.

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 a clear mandatory prerequisite ('ALWAYS pass marketplace + locale') and implicitly defines usage by contrasting it with the general discovery function of search_gifts.

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