fo_list_promotions

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

No annotations are provided, so the description must carry the full burden. It states the tool fetches data, implying a read operation, but does not disclose potential side effects, authentication needs, rate limits, or pagination behavior beyond the schema. The description lacks depth on behavioral traits.

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 two sentences, front-loaded with the primary action, and contains no superfluous information. Every phrase contributes to clarity and conciseness.

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?

With 11 parameters and no output schema, the description explains filtering options but omits details on pagination, result ordering, or the structure of the response. For a list tool, this leaves gaps in completeness, though the schema covers parameter ranges (e.g., max 1000).

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 91%, placing the baseline at 3. The description adds value by clarifying the purpose of couponsOnly and highlighting key filters (advertiser, category, promo type, date range), which helps the agent understand parameter usage beyond schema names.

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?

Clearly states it fetches promotions and coupons from FlexOffers with filtering options. The verb 'Fetch' and resource are specific, but no explicit differentiation from sibling tools like fo_list_advertisers or fo_get_promotion_types, though the context makes it clear.

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?

Provides a usage hint for couponsOnly=true and suggests using fo_get_promotion_types for promo type IDs. However, it does not specify when to avoid this tool or mention alternatives, leaving the agent to infer usage context.

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