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

Annotations only declare openWorldHint and destructiveHint=false, so the description carries most of the load and does it well: it discloses that fixed-price parts are charged immediately against balance or x402, and that quoted parts block until a price arrives and then need accept_quote. That monetary/irreversibility context is exactly what an agent needs before invoking. It omits what happens after the request is created (tracking via get_request/list_requests) and any failure/auth conditions.

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 core purpose is front-loaded, but everything after it is a single dense run-on paragraph of semicolon-separated fragments that is hard to scan and easy to misparse for an 11-mode tool. It is appropriately sized for the breadth it covers; the problem is formatting, not length.

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 23 parameters, nested address objects, 11 modes and no output schema, the description covers mode semantics and the payment/quote lifecycle but not the return behavior (request id, tracking via get_request) or the three catch-all modes. Adequate to start but not complete for a tool this complex.

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 78%, and the description adds real meaning on top: it explains what each action enum value requires (note for digitize, product/value_eur for buy_voucher, what/where/max_price_eur for buy_item) and gives cost implications for same_day, express and registered. It leaves several parameters (shop, carrier, item_id, shipment_id) and three enum values undescribed, so it doesn't fully close the gap.

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?

Opens with a concrete verb and resource ('Ask the human to do something with your mail, documents or parcels') and then enumerates the eleven action modes, which clearly separates it from siblings like buy_bundle, pay_item or announce_shipment. A few modes ('courier, dispose, custom') are named with zero explanation, so the full scope isn't graspable from the description alone.

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?

Usage is implied per action mode rather than stated: pricing and constraints hint at when each applies, and it correctly routes deferred pricing to accept_quote. There is no explicit when-not-use guidance, and no mention of how it relates to nearby siblings such as announce_shipment, get_request or check_inquiry.

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