skip_day

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

With no annotations, the description carries full burden. It discloses the core behavior (moving skipped deliveries to schedule end) and mentions the return format (summary). However, it lacks details on permissions needed, whether changes are reversible, rate limits, or error conditions.

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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value: the first explains the action, the parameter descriptions are essential, and the return statement is helpful.

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 mutation tool with no annotations and no output schema, the description covers the basic operation and parameters adequately. However, it lacks important context about side effects, authentication requirements, and what the 'summary' return contains.

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?

With 0% schema description coverage, the description fully compensates by explaining all 3 parameters: order_id identifies the package, skip_date specifies the date in YYYY-MM-DD format, and order_types clarifies the optional meal types. It adds meaning 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 ('skip deliveries'), the resource ('on a specific date'), and the mechanism ('by moving them to the end of the schedule'). It distinguishes from siblings like 'reschedule_delivery' or 'hold_deliveries' by specifying date-based skipping with schedule adjustment.

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 implies usage for skipping deliveries on a date, but provides no explicit guidance on when to use this tool versus alternatives like 'reschedule_delivery' or 'hold_deliveries'. No prerequisites 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.