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

No annotations provided; description states it is a 'search' (implying read-only) and 'free to call', but lacks details on rate limits, pagination, or auth requirements.

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?

Three short sentences, no fluff. Purpose is first, then usage guidance, then a key parameter detail. Well-structured and efficient.

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 12 parameters, no output schema, and no annotations, the description covers the core idea and one parameter's options. Missing return format and several filter parameters, so moderately complete.

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?

12 parameters with 0% schema coverage. Description adds meaning to 'sort_field' by listing valid values and hints at 'min_profit' and 'min_roi' via example, but many parameters like 'asin', 'limit', 'offset' remain undocumented.

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?

Description clearly states the tool searches Sorsa's A2A deal database with profit, ROI, sales rank, and pricing. It distinguishes from siblings like get_oa_deals and get_store_results by specifying A2A deals.

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?

Explicitly says 'Call when the user asks for current deals' with a concrete example. Does not explicitly exclude alternatives, but the example is helpful.

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