delete_one_time_product

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

No annotations are provided, so the description bears the responsibility for behavioral disclosure. It adds the note 'Disabled in read-only mode,' which alerts the agent to an environment constraint. However, it does not detail other aspects such as irreversibility, permission requirements, or error handling. For a delete operation, this is a minimal but useful disclosure.

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—two short sentences—and delivers the essential purpose and a key constraint without any redundant phrasing. 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?

For a simple delete operation with an output schema, the description is adequate but not complete. It does not mention what happens on success/failure, whether deletion is permanent, or any prerequisites. Given the large sibling toolset, more context about implications might be helpful, but the description covers the core purpose.

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?

The input schema already provides full coverage (100%) with descriptions for both parameters. The tool description adds no further meaning about the parameters, so the baseline score of 3 applies. There is no additional clarity needed beyond what the schema gives.

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 the target resource (one-time product). It distinguishes from similar tools like delete_subscription and batch_delete_one_time_products by specifying singular deletion of a one-time product. The phrase 'from the catalog' adds a clear scope.

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 implicitly indicates use for deleting a single one-time product, which differentiates from batch operations. However, it does not explicitly mention when not to use it (e.g., for multiple products) or alternatives like batch_delete_one_time_products. Still, the singular focus provides clear context.

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