reschedule_delivery

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It mentions the action ('reschedule') and a basic return ('Success or failure message'), but lacks details on permissions, side effects, error conditions, or system constraints like rate limits.

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 parameter and return sections. It's appropriately sized, though the 'Args' and 'Returns' labels are slightly redundant given the structured schema, but they don't detract significantly.

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 5 parameters with 0% schema coverage and no annotations, the description does well on parameters but lacks behavioral context. The output schema exists, so return values needn't be detailed, but overall it's adequate yet incomplete for a mutation tool with no safety disclosures.

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 fully. It provides clear semantics for all 5 parameters, including data formats (e.g., 'YYYY-MM-DD' for new_date) and allowed values for order_type ('LUNCH' or 'DINNER'), adding significant value 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 verb ('Reschedule') and resource ('a single delivery'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'bulk_reschedule' or 'skip_day', which would require mentioning it's for individual deliveries only.

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?

No guidance is provided on when to use this tool versus alternatives like 'bulk_reschedule' for multiple deliveries or 'skip_day' for skipping instead of rescheduling. The description only states what it does, not when it's appropriate.

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