Платформа: информация о заказе

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by specifying the response fields (state, request, courier_order_id) and enumerating possible cancellation reasons (SHOP_CANCELLED, USER_CHANGED_MIND, etc.), which is useful contextual detail beyond the structured metadata.

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 dense sentence that efficiently lists key response elements. It's not overly verbose, though the inclusion of many cancellation reason codes makes it slightly run-on.

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?

For a simple read-only tool with no output schema, the description covers the main output structure and explains possible state reasons. It doesn't explain the slim parameter or request_code filter behavior, but those are documented in the schema, so the description is reasonably complete.

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?

The schema provides complete descriptions for all three parameters (request_id, slim, request_code), so the description adds no additional parameter-level meaning. It mentions courier_order_id, but that is an output field, not a parameter.

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 names the resource (order) and lists the specific contents (state, request, courier_order_id), making it clear this is an order-information tool. However, it uses a noun phrase ('Информация о заказе') rather than an explicit verb like 'retrieve' or 'get', and it doesn't explicitly contrast with sibling tools.

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?

There is no guidance on when to use this tool versus alternatives such as platform_request_history, raw_request, or platform_cancel_request. The description doesn't state prerequisites, exclusions, or typical use-cases.

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