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

With no annotations, the description carries the full burden and does well: it specifies empty-result handling ('show the empty result and ask before trying a different query'), forbids chaining into product-detail tools, and sets an exactly-once rule. It does not mention permissions, rate limits, or whether the carousel is stateful, which are the remaining gaps for an unannotated tool.

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 in sentence one and each subsequent sentence is a concrete directive rather than filler. It runs long (roughly ten sentences) and the repeated prohibitions on rephrasing overlap somewhat, but nothing is pure padding.

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?

An output schema exists, so return-value explanation is correctly omitted, and the search/price/category behaviors are well covered. The only omission is buyer_context, which is undocumented in both schema and description, leaving the agent to guess its shape and effect.

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 83%, so the baseline is 3, but the description adds real meaning: query must be passed verbatim without rewriting, and min_price/max_price are in major currency units with the rule that both set to the same value means an exact price. Only buyer_context goes unmentioned in both places.

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 opening sentence names a specific verb and resource ('Search Aari Clothing and render the interactive product carousel'), and the closing sentences distinguish it from product_details and render_complete_the_look. An agent can differentiate it from every sibling without opening a schema.

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 gives explicit when-to-use ('browsing or discovery'), explicit when-not ('not as a preliminary lookup for an exact product-detail request'), and names the alternative path ('use render_complete_the_look instead'). It even defines call-count policy for single vs. multiple categories and forbids synonym re-searches.

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