find_offers

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

No annotations provided, so description carries full burden. It discloses key behavioral traits: US-delivery-only constraint, that it ends with what was sent to Intent Cloud and what was blocked, and retry semantics for missing details. Doesn't cover auth requirements or rate limits, but the behavioral disclosure is substantial.

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?

Front-loads the core purpose, then provides usage rules and behavioral notes. Mostly efficient, though the sentence about Intent Cloud and blocking could be tighter. Still, every sentence serves a purpose.

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?

No output schema, but the description hints at return content (missing details list, what was sent to Intent Cloud, what was blocked). For a 5-param tool with no required params and no annotations, this does a good job covering the operational context, though more on return format would help.

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 schema already documents all 5 parameters thoroughly. The description reinforces key rules (never guess ZIP or budget, pass only what user said) but adds no syntax or format details beyond the schema.

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 (find) and resource (physical products) with clear scope constraint (ships to a US address). Distinguishes from siblings like create_cart and get_approval_status by being a discovery/search tool rather than a transactional or status tool.

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?

Provides clear instructions on what to pass and when to retry (if result lists missing details, ask user only for those, then call again). Doesn't explicitly name sibling alternatives or state when NOT to use it, but the usage context is clearly conveyed.

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