chitchats_delete_batch

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

Annotations include destructiveHint: true, which already flags the mutating nature. The description adds valuable behavioral context beyond the annotation by specifying the 'empty batch' precondition and the limitation on batches with shipments. It does not contradict annotations and discloses a key operational constraint.

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 exceptionally concise: two short sentences that immediately state the action and the key restriction. Every word earns its place, with no redundant phrasing or unnecessary detail.

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 tool with one parameter, no output schema, and a destructive annotation, the description adequately covers the essential context for selection and invocation. It explains the primary prerequisite (empty batch). It could mention what happens if a non-empty batch is attempted, but given the tool's simplicity, current detail is sufficient.

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 has 100% coverage: the single parameter 'id' is described as 'Batch ID'. The description does not add additional parameter-level details, but since the schema fully documents the parameter, a baseline score of 3 is appropriate.

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 'Delete an empty batch' with a specific verb (delete) and resource (batch), and distinguishes it from other operations by adding the 'empty' constraint. This differentiates it from sibling tools like chitchats_delete_shipment and batch modification tools.

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 clear usage context by explicitly stating that only empty batches can be deleted, and that batches with shipments cannot be deleted. This implicitly guides the agent to use other tools (like remove_from_batch) for non-empty batches, though it doesn't name an explicit alternative.

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