Delivery: zone schedule [sandbox]

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

Annotations already indicate destructiveHint=true, and description adds that re-uploading overwrites previous schedules, confirming destructive behavior. It also clarifies that the body is an array with no wrapper, which is important for API call structure. No contradiction with annotations.

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?

Description consists of three short sentences, each conveying essential information: purpose, overwrite behavior and partner restriction, and body format. No unnecessary words, and key points are front-loaded.

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?

The description lacks information about return values or error scenarios. Since there is no output schema, the burden is higher. It also doesn't mention prerequisites like having a delivery zone created. This leaves the agent underinformed about the tool's output and potential failures.

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 100% with descriptions for all parameters. Description adds that the body is an array directly without wrapper, which enhances understanding of the 'schedules' parameter beyond schema. Baseline is 3, but the 'no wrapper' note pushes it to 4.

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?

Description clearly states the verb 'Sets the working schedule' and the resource 'delivery zone for a specific day'. It distinguishes from siblings by specifying 'for delivery-service partners only' and noting the body format, which unique among delivery 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?

Description explains when to use (for holiday/weekend schedules) and notes that re-uploading overwrites, implying idempotent-like behavior. It states 'for delivery-service partners only' as a prerequisite, but does not explicitly mention when not to use or list alternative tools.

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