Delivery: upload sorting centers [sandbox]

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

Annotations indicate non-read-only, non-destructive, non-idempotent, open world. Description adds that it creates a task, runs initial validation, and returns a taskID. Consistent with annotations, no contradictions, but doesn't detail side effects beyond creation.

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 is concise with 4 sentences, each essential. Front-loaded with main action. No redundancy.

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?

No output schema, but description notes return of taskID and refers to delivery_get_task for status. Could mention validation failure handling but adequate for sandbox tool.

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 good descriptions. Description adds context for dryRun and idempotencyKey with version info and defaults. For centers, it repeats schema info, but overall adds value beyond 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?

Clearly states the tool creates a task to upload sorting centers with initial validation, returns a taskID, and distinguishes from siblings like delivery_get_task and delivery_add_tags_to_sorting_center.

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?

Explicitly tells when to use this tool (to upload sorting centers), and that after uploading, tags must be assigned with delivery_add_tags_to_sorting_center. Also notes it's for delivery-service partners only.

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