bulk_reschedule

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a mutation operation ('reschedule') but doesn't mention permission requirements, whether changes are reversible, potential side effects on other systems, rate limits, or what happens to deliveries outside the specified order_types. The return statement is minimal.

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 well-structured with a purpose statement followed by Args and Returns sections. Every sentence adds value, though the return statement could be slightly more informative. It's appropriately sized for a 5-parameter tool with no wasted words.

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?

Given the complexity of a bulk mutation tool with no annotations, the description is moderately complete. It covers parameter semantics well and mentions output existence, but lacks crucial behavioral context about permissions, reversibility, and system impacts. The presence of an output schema helps, but the description should provide more operational guidance for a potentially destructive action.

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 description coverage is 0%, so the description must compensate. It successfully explains all 5 parameters with clear semantics: order_id identifies the package, start_date/end_date define the range to reschedule, target_start_date specifies the new date, and order_types provides optional filtering. The format guidance (YYYY-MM-DD) and enum values for order_types add valuable context beyond the bare schema.

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 specific action ('bulk reschedule'), the target resource ('all deliveries within a date range'), and the transformation ('to new dates'). It uses precise verbs and distinguishes itself from the simpler 'reschedule_delivery' sibling tool by emphasizing bulk operations.

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 provides no guidance on when to use this tool versus alternatives like 'reschedule_delivery' or 'hold_deliveries'. It mentions a date range scope but doesn't explain prerequisites, limitations, or appropriate contexts for bulk operations versus individual adjustments.

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