Delivery: upload tariff [sandbox]

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

Adds value beyond annotations: 'Returns 200 on accept', limits (400MB body, 1 million directions), and partner-only restriction. No contradiction with annotations (destructiveHint, readOnlyHint, idempotentHint are consistent). Could mention side effects more explicitly.

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?

Concise with front-loaded main action. Each sentence adds value: action, context, limits, audience, recommendations. Could be slightly more structured (e.g., bullet points) but overall efficient.

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 high-level purpose and limits but lacks output schema details (only 'Returns 200 on accept'). No error info or permission specifics beyond partner. For a complex 8-param tool, more completeness would help, but schema covers parameters well.

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 detailed parameter descriptions. The tool description adds no parameter-specific info beyond schema; it only gives context (body size limit). Baseline of 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?

Clearly states the verb 'Creates or replaces a tariff' and specifies the resource (tariff for delivery service). Distinguishes from siblings by explicitly recommending v2 over v1 and pairing with related tools. Includes scope (controls direction availability, cost, terms).

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 clear context: when to use (to control delivery parameters), target audience (PARTNERS only), and a recommendation (prefer v2 over v1). Suggests complementary tools. Lacks explicit 'when not to use' but limits and audience exclusion suffice.

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