onetime_product_offers_batch_delete

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It only indicates a destructive operation without detailing side effects (permanence, permissions, error handling, rate limits, or partial failure behavior).

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 brief (4 words), which sacrifices necessary detail. While it is front-loaded, it does not provide enough information to earn its place; it omits critical context about the operation and parameters.

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 4 required parameters (including an undescribed array), no output schema, and no annotations, the description is far from complete. It fails to explain the request structure, response, limits, or prerequisite conditions, leaving the agent with insufficient information to safely invoke the tool.

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 50% (only packageName and productId are described). The description adds no parameter-level information; it does not explain the purpose of purchaseOptionId or the requests array, nor how to structure a request for deletion. The agent cannot construct a valid call from the description alone.

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) and resource (offers), with a limit (up to 100). However, it does not specify that these are one-time product offers, relying on the tool name for that context. Among siblings like onetime_product_offers_batch_get and update, the verb distinguishes it, but deeper differentiation from other batch delete tools is missing.

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 guidance on when to use this tool versus alternatives such as onetime_product_offers_batch_update_states or individual delete operations (if they exist). The description does not mention prerequisites, required parameters, or the scenario for batch deletion.

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