Get Amazon.in Product Detail

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral traits: it scrapes the product page, returns a detailed JSON structure, and handles specific errors (bot-check page with retry suggestion). This provides context beyond annotations.

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?

The description is well-structured: starts with the core purpose, then lists return fields, then error handling. It is front-loaded with the main action. Slightly verbose due to listing all return fields, but each provides necessary context.

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 the tool has no output schema, the description compensates by listing every return field with types and names. It also explains error handling with specific messages. For a single-parameter tool, this is comprehensive and covers the full usage context.

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% with a clear description of the parameter. The description adds value by explaining the input format: plain 10-char ASIN or a URL containing /dp/<ASIN>, with an example. This clarifies the acceptable inputs beyond the schema's min/max length.

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 it fetches a single Amazon.in product detail by ASIN or URL, specifying the resource (product detail) and action (fetch). It differentiates from sibling tools like search_amazon_in which is for searching, and price_history_link which likely returns historical pricing only.

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?

The description explicitly says to fetch a single product detail, and mentions error cases like invalid ASIN or bot-check page, implying retry. It does not explicitly say when not to use, but the context of fetching a single product vs. searching is clear from the sibling tool names.

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