Delivery: upload pickup points [sandbox]

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

Annotations indicate destructiveHint=true and readOnlyHint=false; the description adds that the tool replaces the entire terminal set and auto-approves or queues for manual review. It also notes the tool wraps the request body, providing added behavioral context beyond 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?

The description is concise (3 sentences) and front-loaded with the core action. Every sentence adds meaningful information with 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?

Tool lacks output schema, but the description explains the possible responses (200 or manual review queue). It covers the key behavioral outcome, though details on return structure are omitted. For a sandbox tool with complex input, it is reasonably complete.

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%, so parameters are already documented. The description adds minor value ('the tool wraps it for you') but does not elaborate on parameter semantics beyond the schema. Baseline 3 is appropriate.

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 (uploading pickup points/parcel lockers). It specifies the resource (terminals for one tariff) and distinguishes from siblings like delivery_add_areas_sandbox or delivery_add_tariff_sandbox_v2 by focusing on terminal uploads.

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?

Describes the behavior (auto-approve vs manual review) and restricts usage to delivery-service PARTNERS. However, it does not explicitly compare to alternative tools for adding terminals such as delivery_add_areas_sandbox or delivery_add_tariff_sandbox_v2, missing when-not-to-use guidance.

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