tiendanube_list_discounts

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

The description only says 'read-only.' No annotations provided, so it fails to disclose pagination behavior, rate limits, empty responses, or other side effects beyond the read-only hint.

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?

Extremely short but at the expense of useful information. 'LIST DISCOUNTS' is redundant with the tool name. Not concise in a helpful way.

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 no output schema, no parameter descriptions, and minimal behavioral info, the description is far from complete. It omits key details about how to use the tool effectively.

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?

0% schema coverage and description provides no explanation of the four parameters (page, per_page, fields, since_id). The agent has no clue what they mean or how to use them.

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 it retrieves store discounts and is read-only. The verb 'list' matches the tool name and distinguishes from sibling tools like 'get_discount' (individual) and 'list_coupons' (different entity).

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?

No guidance on when to use this tool vs alternatives (e.g., use 'get_discount' for a single discount, or 'list_coupons' for coupons). No context for filtering or pagination.

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