Delivery: parcel change result

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

Annotations already declare readOnlyHint=false (write operation) and destructiveHint=false. The description adds that it sends data to Avito and that regular accounts receive 403/404, but does not fully disclose side effects (e.g., idempotency behavior, rate limits, or what happens on failure beyond the 403/404 note).

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 two sentences long, with the first sentence front-loading the core purpose and context, and the second adding a relevant behavioral note. No redundant or unnecessary information.

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 6-parameter schema with 100% coverage and no output schema, the description covers the main action and important context (3PL, production method behavior). It lacks details on error responses beyond 403/404 and does not address the openWorldHint annotation, but is otherwise sufficient.

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% with detailed parameter descriptions. The description does not add extra meaning beyond the schema; it only mentions the status values approved/declined which are already in 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 sends the outcome of a parcel change request to Avito, specifies the two possible statuses (approved/declined), and distinguishes it from the sibling delivery_change_parcels which sends the initial request. The '[3PL]' prefix and mention of 'on a regular seller account it returns 403/404' further clarify its intended context.

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 explicitly says it should be used after delivery_change_parcels, providing a clear usage context. It implies that the tool is for 3PL accounts by noting that a regular seller account gets 403/404, but does not explicitly mention when not to use it or list alternative tools.

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