Delivery: set parcel properties [sandbox]

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

The description claims idempotent behavior ('Idempotent by overwrite'), but annotations set idempotentHint=false, a direct contradiction. This undermines trust. Annotations already indicate destructiveHint=true, so the overwrite disclosure adds value, but the idempotency contradiction is a serious flaw.

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?

Two focused sentences plus a sibling comparison. No filler, front-loaded with purpose and audience, every sentence adds value.

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 purpose, audience, usage guidelines, important behavioral nuance (overwrite), and sibling differentiation. Minor gap: no mention of output (returns empty 200) is fine since no output schema. The annotation contradiction slightly reduces completeness but overall is adequate.

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 descriptions for each parameter. The description adds no parameter-level detail beyond the schema, but the overwrite instruction contextualizes usage of the 'properties' object. 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 sets parcel delivery parameters (e.g., final delivery cost) on Avito, specifies it is for delivery-service PARTNERS only, and distinguishes from siblings (address setting and tracking).

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?

Explicitly tells when to use (set cost/parameters), provides a critical usage instruction (send complete set, not delta due to overwrite), and clarifies what it is not for (address or tracking) with sibling references.

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