Delivery: upload sorting centers [sandbox]

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

The description notes it's in sandbox mode, creates a task with initial validation, and returns a taskID. Annotations already indicate it's a write operation (readOnlyHint=false). It does not explain what the validation entails, the asynchronous nature, or potential errors beyond the idempotencyKey conflict hinted in schema.

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 (three sentences) and front-loaded with the main action. It includes key constraints and next steps without fluff. Some may argue it could be slightly more structured, but it's effective.

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 the tool's relative simplicity (3 parameters, no output schema), the description covers the async nature, eligibility, and post-upload step. It lacks details on validation outcomes, but the reference to checking status via delivery_get_task provides a path. Overall adequate for the 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% with descriptions for all parameters. The description adds minimal value by stating 'the body is an array of sorting centers directly,' which is already evident from the schema. It does not explain how to structure each center beyond the 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 tool creates a task to upload sorting centers, with validation and taskID return. It distinguishes from siblings like delivery_get_task and delivery_add_tags_to_sorting_center, though the exact resource ('sorting centers') is somewhat vague.

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 specifies the tool is for delivery-service partners and mentions the subsequent step of assigning tags. However, it does not explicitly state conditions when to use or avoid this tool compared to others, and lacks guidance on prerequisites like having a profile.

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