onetime_product_offers_list

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

No annotations are provided, so the description must disclose behavioral traits. It indicates a read operation ('list') but fails to mention pagination behavior (despite pageSize/pageToken in schema) or any other side effects. The description lacks important context required for safe and correct invocation.

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 a single sentence with no unnecessary words. It front-loads the key action and includes a critical usage hint, using backticks for code clarity. Every word earns its place.

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 that there is no output schema, the description should explain what the tool returns. It does not mention return format or pagination. Additionally, with 5 parameters (3 required), only one parameter's usage is clarified. The description is insufficient for an agent to fully understand the tool's behavior.

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 low (40%), and the description adds meaning for purchaseOptionId by explaining the special '-' value, which the schema did not describe. However, it does not clarify optional parameters pageSize or pageToken, leaving some gaps. The addition is helpful but partial.

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 the tool lists offers attached to a purchase option. It uses a specific verb ('List') and resource ('offers'), and the presence of sibling tools like onetime_product_offers_get and onetime_product_offers_batch_delete indicates this is distinct for listing, not single retrieval or batch operations.

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 implies usage by stating 'purchaseOptionId is required' and that '-' can be used to list across all options. However, it does not explicitly differentiate this tool from related alternatives like onetime_product_offers_get or onetime_product_offers_batch_get, nor does it specify when not to use it.

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