get_flash_deals

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

With no annotations provided, the description carries the burden and partly compensates: it discloses authentication needs, pagination behavior, default listId, and the return schema. It does not mention error behavior or rate limits, but for a read-only fetch tool, this is reasonably transparent.

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 three sentences, front-loaded with the core purpose, then return details, then authentication and the critical cart-add warning. Every sentence earns its place with no filler or redundancy.

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 paginated read tool, the description covers the essential context: what it fetches, what it returns, authentication, and a critical cross-tool caveat. It does not mention sorting or failure modes, but the low complexity and good schema coverage make it sufficiently 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 description coverage is 100%, so the baseline is 3. The description adds minimal semantic value beyond the schema, only reinforcing that listId '157975' is the flash deals collection. No parameter-level details are explained beyond what the schema already contains.

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 uses a specific verb 'Fetch' and a clear resource 'today's Mega Flash Deal products', explicitly distinguishing it from sibling tools like list_products and search_products. It also lists the output fields (name, weight, MRP, selling price, discount %, stock status), leaving no ambiguity about what the tool does.

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 states a prerequisite ('Requires authentication') and provides explicit guidance for a related action: 'To add any product from this list to the cart, always use add_flash_deal_to_cart — never use add_to_cart for flash deal items.' It doesn't contrast with list_products for fetching non-flash deals, but the warning about the cart is a clear when-not/alternative.

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