Платформа: рассчитать варианты доставки

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

The description adds important behavioral context beyond annotations: the order is not created until confirmation, offer is valid until expires_at, and money amounts are in kopecks. It also exposes the specific error case. While it doesn't enumerate all side effects, it clarifies the state lifecycle.

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 a single, focused paragraph that front-loads the main purpose, then packs essential details (response structure, workflow, error, units) without redundancy or fluff.

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 lack of an output schema, the description provides a partial response structure, error handling, and workflow context, which is substantial for a 10-parameter tool. It misses explicit alternatives to express tools, but the sibling list helps fill that gap.

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 each parameter is already explained in the schema. The description adds cross-cutting details (kopecks, error condition) but does not provide per-parameter meaning beyond what the schema offers, so 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 it calculates delivery options (offers) for 'another day' orders, using specific verbs and resources. It also distinguishes itself from the sibling tool platform_confirm_offer by explaining that the selected offer is booked there.

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?

It explicitly describes the workflow: calculate offers first, then use platform_confirm_offer to book. It also provides an error condition (400 no_delivery_options) for when no options exist. However, it does not explicitly contrast with express delivery siblings, so exclusion guidance is missing.

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