batch_dispatch

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

Annotations already declare destructive=true and openWorldHint=true, but the description adds critical context they don't convey: the call MOVES MONEY, it handles up to 25 deliveries at once, and it mandates summarizing count/destinations/fees and obtaining explicit user confirmation first. That is exactly the behavioral detail an agent needs to avoid an irreversible mistake.

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?

Front-loaded with the core action, then required item fields, then the safety warning. Every sentence adds information an agent needs; the capitalized money-movement warning is intentional emphasis, not padding.

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?

With no output schema, the description still explains the return shape (a batch_id plus one result per delivery), and for a destructive, money-moving mutation it supplies the required fields, the confirmation protocol, and the batch limit. Nothing an agent needs to invoke it safely is missing.

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 0% and the deliveries array has no item schema, so the description carries the full burden — and it does: it enumerates the required item fields (external_delivery_id, dropoff_address, dropoff_phone_number, order_value in cents), marks tip as optional, and explains that top-level pickup_address applies only to items that don't set their own.

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?

States a specific verb (dispatch) plus scope (up to 25 deliveries at once) and concrete use cases (catering runs, multi-order drops), which cleanly separates it from the single-delivery sibling dispatch_delivery.

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?

Gives clear context for when to use it (batches up to 25, catering/multi-order drops) and adds a mandatory confirmation workflow before dispatch. It does not explicitly name or exclude alternatives like schedule_batch, so it falls short of full routing guidance.

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