Search Amazon.in

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

The description discloses it works without sign-in and lists returned fields, but lacks details on rate limits, pagination, or error behavior. Without annotations, more transparency on potential side effects or limitations would be beneficial.

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 concise sentences that front-load the action and return fields, with no unnecessary information. Each sentence serves a clear 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?

For a simple search tool with good schema coverage, the description adequately covers the purpose, inputs, and outputs. However, it could mention pagination handling or error scenarios to be fully 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?

Schema coverage is 100%, and the description adds minimal extra meaning beyond what is already in the schema (e.g., example query). The parameter descriptions in the schema are sufficient, so the description does not significantly enhance parameter understanding.

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 clearly states the action ('Search Amazon.in for products') and lists specific return fields like title, price, rating, etc. This distinguishes it from sibling tools which focus on orders, login, or browser state.

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?

No guidance on when to use this tool versus alternatives. The description notes it works without signing in, but does not explicitly state when not to use it or provide context for choosing it over other tools.

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