batch_delete_purchase_options

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

No annotations exist, so the description bears full responsibility. It only mentions 'disabled in read-only mode', which is a behavioral constraint. It does not disclose that the operation is destructive, any permission requirements, potential side effects on related data, or partial-failure behavior. For a delete operation, this is insufficient.

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?

Two concise sentences with no filler. The description is front-loaded and every word serves a purpose. It gets straight to the point.

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?

Despite having an output schema and 100% schema coverage, the description omits important contextual details for a delete operation, such as rollback behavior if some items fail, impact on existing purchase states, or idempotency. The brevity leaves gaps that could affect the agent's decision-making.

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 100% and each parameter has a description in the schema. The tool description adds no parameter-specific info beyond what the schema already provides. Baseline of 3 is appropriate since the schema fully documents the parameters.

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 (delete), resource (purchase options), and scope (from a one-time product, batch operation). It distinguishes this tool from siblings like batch_delete_one_time_products and batch_delete_purchase_option_offers by specifying the exact entity and context.

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 gives a context (batch operation on purchase options) but does not explicitly state when to use it over alternatives or mention any exclusions. The 'disabled in read-only mode' is a constraint, not usage guidance. Sibling tools are not referenced, so the agent must infer usage from the name.

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