myntra_search

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

No annotations are provided, so the description carries full burden. It mentions credits cost and output format (parsed JSON by default, or HTML if html=true). However, it lacks details on error handling, rate limits, or any destructive behavior (though scraping is presumably read-only).

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 informative but verbose, especially the extensive return structure example. It is front-loaded with purpose, but the length could be reduced without losing clarity. Several sentences could be condensed.

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 no output schema, the description provides a thorough breakdown of the return object fields. Parameters are fully covered. However, it missing information about pagination or how to retrieve additional results, which would be expected for a search tool.

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?

Input schema has 100% coverage, but the description adds meaning by specifying that the url must be a full pre-built Myntra search URL with rawQuery and filters, and explains the html parameter. This provides context beyond the schema descriptions.

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 scrapes Myntra search result pages by passing a search URL, and lists extracted data (product IDs, names, brands, prices, etc.). It distinguishes from sibling tools like myntra_product by focusing on search results.

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 explains how to use it (pass a full pre-built Myntra search URL) but does not explicitly state when to use this tool vs alternative shopping search tools or provide exclusion criteria. The context is implied by the platform-specific name.

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