tiendanube_list_coupons

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

No annotations provided, so the description carries the full burden. It states it retrieves a list with filtering but does not disclose any behavioral traits like pagination behavior, auth requirements, rate limits, or side effects (though it's a read operation). Adequate but not rich.

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?

Description is concise, starting with purpose in bold and emoji, followed by use cases. Every sentence adds value; no filler. Could be slightly shorter but efficient.

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?

Given 11 parameters and no output schema, the description lacks details on return format or pagination behavior. It mentions filtering and use cases but does not cover what the list response looks like or any limits. Adequate but incomplete for a comprehensive list tool.

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 schema already documents all parameters. The description mentions 'advanced filtering options' but adds no specific parameter information beyond what the schema provides. Baseline 3 is appropriate.

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 'LIST ALL COUPONS' and specifies the resource (discount coupons) and action (retrieve comprehensive list). It lists use cases, distinguishing it from other list tools by resource type. The verb is specific and the resource is unambiguous.

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 provides explicit use cases like promotional campaign management, coupon analytics, expired coupon cleanup. It implies when to use this tool for comprehensive retrieval but does not exclude alternatives like get_coupon for single coupon retrieval. No explicit when-not or comparison to siblings, but context is clear.

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