list_flash_price_campaigns

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

With no annotations, the description carries the full burden. It discloses the return structure (dict with total_found, returned, items[] and field names) and the underlying API endpoint. It does not mention pagination, ordering, or authorization, but for a read-only list operation, this is adequate.

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 with clear sections (purpose, API, return structure) and is concise. There is minor redundancy between the opening line and the purpose section, but overall it is efficient and organized.

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?

The tool is simple, and the description provides the return structure (compensating for the absence of an output schema), explains the purpose, and suggests the detail tool. It could mention pagination behavior, but the max_results parameter in the schema covers that, so the description is 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?

The schema already documents the only parameter (max_results) with a description, so the description adds no additional parameter meaning. With 100% schema coverage, the baseline of 3 applies.

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 tool retrieves a list of flash price campaigns, specifies the scope (all flash sales with name, status, time range), and distinguishes it from get_flash_price_campaign_detail by explaining that campaign_id can be used for further detail lookup.

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?

It provides a clear usage context (browsing all flash sale campaigns) and explicitly points to get_flash_price_campaign_detail as the next step for full details, implying when to use each. However, it does not discuss alternatives like list_promotions or search_promotions, so it's not a full exclusionary guide.

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