Delivery: set parcel properties [sandbox]

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

The description claims 'Idempotent by overwrite', but the annotation 'idempotentHint' is false, creating a contradiction. It does add context about return value (empty 200) and partner-only access, but the inconsistency reduces credibility.

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: two sentences plus a sibling list. It is front-loaded with the core action and efficiently conveys idempotency behavior, audience, and comparison to siblings.

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?

Given the tool has 4 parameters, 100% schema coverage, and no output schema, the description covers target audience, behavioral specifics (overwrite semantics), return value, and sibling differentiation. The idempotency contradiction slightly diminishes completeness.

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 description coverage is 100%, so the schema already documents each parameter. The description adds no new parameter-level insights beyond stating that 'properties' contains delivery parameters. 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 a parcel's delivery parameters (cost/parameters) on Avito. It distinguishes from sibling tools by naming them and specifying that this tool only sets cost/parameters, not addresses or status events.

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 provides explicit usage guidelines: it is for delivery-service partners only (not regular sellers), it must always send the complete current set (not a delta), and it contrasts with sibling tools for when to use alternatives.

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