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

With no annotations supplied, the description carries the full burden and does disclose key behavior: empty results are shown as-is and require confirmation before retrying, and results must not be fed into detail tools. It does not state the hard cap of 10 results or anything about latency/availability, so disclosure is strong but not exhaustive.

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?

Purpose is front-loaded and the dense rule list is mostly operational rather than filler. There is some repetition around not rephrasing or repeating searches across two separate sentences that could be merged.

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 an output schema present, return values need no explanation, and the description covers the search, budget, and anti-chaining behaviors thoroughly. The only uncovered element is the buyer_context parameter, which no field documents.

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 high (83%), so baseline is 3, and the description earns above that by adding the pass-through rule for query and the non-obvious rule that min_price and max_price should be set to the same value only for an exact price. The buyer_context object remains unexplained in both schema and description.

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?

"Search Dream Is Free and render the interactive product carousel" gives a concrete verb, resource, and rendered output in one clause. It also distinguishes itself from siblings by naming product-detail lookups and render_complete_the_look as the correct path for other intents.

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?

Explicit when-to-use (browsing/discovery, not a preliminary lookup for an exact product request), when-not-to-use (don't auto-open product-detail tools to rank or validate), and the alternative for pairing scenarios (render_complete_the_look). It also sets call-count rules per category and forbids synonym/colour/style rewrites.

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