Delivery: zone schedule [sandbox]

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

Annotations indicate destructiveHint=true, and the description confirms this by stating re-uploading overwrites previous schedule. It adds structural context (body is array directly, no wrapper) and sandbox indication. 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?

The description is extremely concise with two sentences and a final note. It front-loads the main purpose and avoids unnecessary words. Every sentence adds value.

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 covers purpose, overwriting behavior, target audience, and body structure. It does not describe the output or error scenarios, but given no output schema, this is acceptable. It is sufficiently complete for the tool's complexity.

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%, so baseline is 3. The description adds a note about the body structure (array directly, no wrapper), which is useful but not critical. Parameter details are adequately covered in 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 'Sets', the resource 'working schedule of a delivery zone', and specifies the use case for dates differing from regular schedule (e.g., holidays/weekends). It distinguishes this tool from regular schedule setting and indicates it's for delivery-service partners 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?

The description provides context on when to use (for differing schedules) and states that re-uploading overwrites. However, it lacks explicit guidance on when not to use or alternative tools. The mention of 'For delivery-service partners only' sets some boundaries.

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