Delivery: upload pickup points [sandbox]

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

Annotations already indicate destructive and non-read-only behavior. The description adds valuable details: the tool replaces the terminal set (destructive), auto-approves or queues for manual review, and wraps the request body. No contradictions.

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?

Three sentences, front-loaded with the core action, then sandbox behavior and partner restriction. No redundant information. Every sentence earns its place.

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?

Covers the main aspects: action, sandbox environment, auto-approve vs manual review, partner restriction, and request body handling. Could mention what 'critical changes' means, but overall sufficient for an agent.

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 has 100% coverage with descriptions for all 4 parameters. The description adds the insight that 'the request body is the terminals array directly (the tool wraps it for you)', which clarifies the interface 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 'Replaces the tariff's terminal set' and 'Uploads terminals (pickup points / parcel lockers) for one tariff'. It distinguishes itself from siblings like delivery_add_areas_sandbox by specifying its exact resource and action.

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?

Provides context on when auto-approval occurs vs manual review, and restricts usage to 'delivery-service PARTNERS only'. However, it does not explicitly state when not to use it or compare to siblings like delivery_add_tariff_sandbox_v2.

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