Batch Delete In App Products

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

No annotations are provided, so the description carries the behavioral burden. It clearly identifies the operation as destructive ('Delete') and adds a concrete guardrail ('Disabled in read-only mode'). It does not detail irreversibility or partial-failure behavior, but the core behavioral context is present.

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 sentences with zero filler. The primary action is front-loaded, and the important read-only mode constraint is included efficiently in the second sentence.

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 batch delete with fully documented parameters and an output schema, the description gives enough context to select and invoke the tool. The main gap is the lack of explicit guidance on when to use this versus delete_in_app_product, but the essential call semantics and guardrail are covered.

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 documents both parameters at 100% coverage with clear descriptions: 'List of product SKUs to delete' and 'App package name'. The tool description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 uses a specific verb and resource ('Delete multiple in-app products') and clearly conveys batch scope, distinguishing it from delete_in_app_product and other delete_* siblings. The 'single operation' phrasing clarifies the batching behavior.

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 batch intent is implied by 'multiple' and 'single operation', but the description does not explicitly tell the agent when to prefer this tool over delete_in_app_product or when not to use it. No alternatives or exclusions are mentioned.

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