get_product_promos

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

The description implies a read-only operation and lists the kind of promotional data returned, but it does not disclose side effects, error behavior, authentication requirements, or output structure. Since no annotations are provided, some behavioral details are missing.

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 a single, clear sentence with no redundant or vague phrasing. It efficiently communicates the tool's purpose and the main data points covered.

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 tool with one input parameter and no output schema, the description provides sufficient context about what the tool returns (vouchers, promotions, discounts, expiry dates). It does not describe the exact response format, but that is not critical for this simple use case.

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 input parameter 'product' is fully described in the schema, including its type, requirement, and acceptable forms (slug or URL). The tool description adds no extra parameter meaning, so the baseline score 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's action ('List') and resource ('vouchers and promotions a Toco listing is currently eligible for'), and it is distinct from sibling tools like get_product_detail or get_product_variants by focusing specifically on promotional offers.

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 intended use is implied by the description, but it does not explicitly explain when to choose this tool over alternatives such as get_product_detail or search_products. There is no direct comparison or condition stated.

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