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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds 'leitura' (read) and mentions bulk execution, but these do not contradict annotations and offer minimal additional transparency about side effects.

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 short but poorly structured, listing multiple actions before flattening to 'list'. This creates confusion rather than clarity. The key information (that it lists coupons) is buried in Portuguese and redundancy.

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 the simplicity of a list operation, the description is incomplete: it does not clearly state what is returned, how pagination works, or what 'account' filters mean. The contradictory action list further reduces completeness.

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 schema has four parameters (id, ids, cursor, account). The description only indirectly mentions id and ids via the action list and 'bulk support', and cursor is referenced as part of 'list (cursor)', but account is completely unexplained. Coverage is low and confusing.

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 says 'Cupons no Guru (leitura)' (read coupons) but then lists multiple actions (list, get, audits, transactions) before clarifying '[Flattened action: list]'. This ambiguity obscures the actual purpose, which is to list coupons, and fails to distinguish it from sibling tools like guru_coupons_get.

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 explicit guidance on when to use this tool versus alternatives. It mentions bulk support for ids, but does not explain scenarios (e.g., listing vs. fetching a single coupon) or how it relates to other coupon tools.

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