onetime_products_list

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

No annotations exist, so the description carries full burden. It only says 'List all one-time products' without disclosing that it is a read operation, whether pagination is involved (despite pageSize and pageToken parameters), or any rate limits or authentication needs. The minimal description leaves critical behavioral traits unaddressed.

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 extremely concise (one sentence). While front-loaded, it is under-specified; crucial details like pagination and required context are omitted. It earns a 3 because it is short and to the point but lacks necessary substance.

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 complexity (3 parameters, no output schema, no annotations, and a domain-specific context), the description is completely inadequate. It fails to explain the return structure, pagination behavior, or the meaning of pageSize/pageToken. An agent cannot reliably invoke this tool without additional knowledge.

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 only 33% (only packageName described). The description adds no parameter information, leaving pageSize and pageToken unexplained. With low coverage, the description should compensate but does not, so it adds minimal value beyond the schema.

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 verb 'list' and the resource 'one-time products', indicating a listing operation. However, it uses 'all' which may mislead about pagination, and it doesn't specify the scope (e.g., filtered by packageName) despite the required parameter. It distinguishes from sibling tools like onetime_products_get (single item) but not from onetime_products_batch_get (batch retrieval).

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 usage guidelines are provided. The description does not mention when to use this tool versus alternatives like onetime_products_batch_get, nor does it explain prerequisites (e.g., packageName required). The agent receives no context for tool selection.

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