Coupons List

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful operational context beyond annotations: the required read_coupons scope, API version 2025-03, and return envelope. It does not discuss rate limits or pagination nuances, so 4 is appropriate.

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?

Front-loaded with the core action, followed by compact and relevant operational metadata. There is no filler; every line (endpoint, scope, version, return shape) is useful.

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 filtered-list tool with 18 optional parameters and no output schema, the description supplies the endpoint, required scope, API version, and return envelope. The schema handles filters and annotations handle safety, but the description lacks sibling-routing guidance for get vs list, leaving a small gap.

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?

All 18 parameters have schema descriptions, so the schema carries the parameter semantics. The description adds no parameter-specific meaning; it only describes the response shape and endpoint. Baseline 3 fits when schema coverage is 100%.

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?

States a specific verb and resource ('List coupons') and includes the HTTP endpoint, so the core operation is clear. It does not explicitly differentiate from the sibling tiendanube_coupons_get or clarify filtering scope, so it falls short of a 5.

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 no when-to-use guidance, prerequisites, or alternatives. An agent must infer that this is for browsing/filtering coupons rather than fetching one by ID, and no exclusion points to tiendanube_coupons_get is given.

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