run_flipkart_seller

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return payload's fields and the billing model ('Flat 5 points per successful run'), which the schema does not cover. It omits auth/rate-limit details, so it 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?

Front-loaded with the core action and resource, followed by the return fields and cost in a compact two-sentence block. The attribute list is slightly run-on but each item carries informational weight given there is no output schema.

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 one-parameter, no-output-schema tool, the description tells the agent what it gets back and what it costs, which is the material context. The only omission is any indication of error/empty cases (e.g. product without a seller).

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 single 'product' parameter is already documented with an example (itm4d0125d9c2c65). The description only references 'a given product' without adding format or syntax meaning beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb ('Get') and resource ('the Flipkart seller offering a given product') and enumerates the returned attributes (name, rating, years on Flipkart, units sold, quality/speed scores, ratings, description). This clearly distinguishes it from sibling run_flipkart_product, which returns the product rather than its seller.

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?

Usage is implied: pass a product to obtain the seller behind it. However, it never states when to prefer this over run_flipkart_product, run_flipkart_product_search, or other marketplace seller tools, and gives no prerequisites. Adequate but with clear gaps.

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