List offer codes

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds meaningful context beyond that: the OAuth scope required (edit_products) and that no local effect approval is needed, both of which affect how an agent may invoke it.

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 tight clauses with the purpose front-loaded, then endpoint/scope, then approval note. Nothing is padded, though 'Reviewed native GET' is slightly jargon-heavy for an agent that only needs the operation semantics.

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?

No output schema exists, so return-value detail is not required, and annotations carry the safety profile. The scope and approval notes round out what an agent needs, though pagination or result-volume behavior for a list endpoint is not mentioned.

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%, with both parameters (account, product_id) documented in the schema including pattern and length constraints. The description adds no parameter syntax or format detail beyond the endpoint path, so the baseline of 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?

States a specific verb+resource ('List offer codes') and identifies the native endpoint GET /products/:product_id/offer_codes, which clarifies it is a product-scoped collection listing. It is distinguishable from siblings like get_offer_code, create_offer_code, and delete_offer_code, though it never explicitly names those alternatives.

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 supplies a required scope (edit_products) and notes no local approval is needed, which is useful precondition context. However, it never says when to use this versus get_offer_code (single) or the create/update/delete siblings, so usage is only implied.

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