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

No annotations are provided, so the description carries the full behavioral burden. It describes the operation at a high level but does not disclose whether the tool is read-only, what constitutes a successful response, how errors/manifestations are handled, or any other behavioral traits. The description adds no transparency beyond the action itself.

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 one short front-loaded sentence plus a price indication. It contains no fluff and gets directly to the purpose. However, its conciseness borders on under-specification, so it does not earn a 5.

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 output schema, annotations, and meaningful parameter documentation, the description is incomplete for actual tool invocation. An agent would not know exactly what to place in the generic 'args' object or what response shape to expect. The description serves as a label but not as a complete spec.

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 input schema is a generic wrapper with 'args' and 'extra' objects, and schema description coverage is 0%. The description does imply that a track number is needed, but it never explains how to pass it into 'args', what key name to use, or what other values are expected. This is not sufficient for an agent to construct a correct call.

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 identifies a specific action ('отслеживание' / tracking), a specific resource ('отправления' / shipments), and the required key ('по трек-номеру'). This clearly differentiates it from sibling Rospochta tools like pochta_address, pochta_tariff, and pochta_delivery_time, which handle different services.

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 phrase 'по трек-номеру' implies this tool is used when a Russian Post tracking number is available, but the description gives no explicit when-to-use or when-not-to-use guidance, and does not contrast with alternative pochta_* siblings. Usage is implied rather than instructed.

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