List discounts

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

Without annotations, the description discloses cursor pagination, API documentation reference, and verbatim error forwarding on 400s, plus fetch_all behavior with a safety cap. This adds meaningful behavioral context beyond the schema.

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?

Three concise sentences front-load the purpose and method, then add pagination and error-handling details without any wasted words.

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 no output schema, the description provides useful pagination and error context but lacks explicit description of the return structure. Still, it sufficiently covers the tool's behavior for a list endpoint.

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 coverage is 100% with detailed descriptions. The description adds value by explaining error handling and reinforcing fetch_all's pagination logic, offering context beyond the schema's parameter descriptions.

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 discounts from Loyverse (GET /discounts)' with a specific verb and resource, distinguishing it from siblings like loyverse_get_discount or loyverse_create_discount.

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 mentions pagination support and error handling (400 responses), but does not explicitly guide when to use this list tool versus get, create, or other list tools, nor provides when-not-to-use advice.

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