onetime_products_batch_delete

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

No annotations provided. The description implies a destructive write operation but lacks details on behavior such as partial success handling, idempotency, or permission requirements.

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 concise sentence. However, for a batch operation, slightly more detail could improve clarity without adding unnecessary length.

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 of a batch delete operation, the description lacks important details about request structure, limits, error handling, and expected behavior. No output schema is provided.

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 50% (only packageName described). The description does not add meaning to the 'requests' array parameter, leaving ambiguity about its format and required structure.

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 action (Delete), the resource (one-time products), and the batch nature (up to 100 in one call). It distinguishes itself from the sibling tool 'onetime_products_delete' which deletes a single product.

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?

There is no guidance on when to use this tool vs alternatives like 'onetime_products_delete' for a single item, or 'onetime_products_batch_update'. No context on prerequisites or limitations.

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