Delivery: zone schedule [sandbox]

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

The description discloses the destructive behavior (overwrites previous schedules) and the sandbox environment, adding value beyond annotations. It does not contradict the annotations (destructiveHint=true). It could mention authentication or rate limits, but overall transparency is good.

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 concise with three focused sentences: purpose, overwrite behavior and scope, and body format. No unnecessary words, and the key information is 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?

Given no output schema, the description covers purpose, behavior, scope, and input format. It does not describe return values or error handling, but for a sandbox tool with clear annotations, this is sufficient.

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 100% schema description coverage, the schema already documents parameters. The description adds clarity by noting that the body is 'an array of schedules directly (no wrapper),' which helps the agent understand the input format beyond what the schema provides.

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 tool sets a custom working schedule for a delivery zone on specific days (e.g., holidays). It distinguishes the custom schedule from the regular schedule and specifies it's for delivery-service partners, making the purpose unambiguous.

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 by noting the tool is for delivery-service partners and mentions that re-uploading overwrites previous schedules. However, it does not explicitly state when to use this tool versus alternatives like delivery_add_areas_sandbox or delivery_add_tariff_sandbox, so guidance is clear but lacks exclusions.

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