Delivery: upload pickup points [sandbox]

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

Annotations already indicate destructive and non-idempotent behavior. The description adds valuable context: 'Replaces the tariff's terminal set' (destructive), the auto-approval vs. manual review process, and partner-only restriction. No contradictions 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?

Three sentences with no wasted words. The description is front-loaded with the primary action, includes the [SANDBOX] tag, and provides essential behavioral details efficiently.

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?

While input schema coverage is 100% and annotations are present, the description lacks information about the response format or error cases. For a tool that replaces a terminal set, an agent would benefit from knowing what the 200 response contains or what triggers manual review.

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%, but the description adds the crucial hint that the request body is the terminals array directly (the tool wraps it). This clarifies that the main payload is the terminals parameter, adding meaning 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 by uploading terminals (pickup points/parcel lockers). The verb 'replaces' and resource 'terminals for a tariff' are specific, and it distinguishes from sibling tools like delivery_add_areas_sandbox which deal with areas, not terminals.

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 it is for 'delivery-service PARTNERS only' and explains auto-approval vs. manual review. However, it does not explicitly state when not to use this tool or suggest alternatives among the many delivery siblings, leaving usage guidance incomplete.

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