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

With no annotations, the description carries the full burden. It does disclose the cost ($0.01 USDC) and the two lookup modes, which is useful. However, it does not state that this is a read-only operation, describe the response format, or mention any rate limits or error behavior. The lack of explicit safety information is a gap, though the tool name suggests a non-mutating lookup.

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 efficient sentence followed by the cost, with no superfluous words. It front-loads the primary purpose and includes the pricing information. While it is brief, every element earns its place.

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?

The tool has no annotations, no output schema, and low parameter coverage; the description does not mention return value format, pagination behavior, or how conflicting inputs (both postal_code and coordinates) are handled. An agent would have to guess or experiment to fully understand the tool's behavior.

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 0%, so the description must compensate. It explains postal_code and coordinates (latitude/longitude) but does not clarify the meaning of 'top' (the maximum number of results). This leaves one parameter semantically unexplained, and the description only partially maps to 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 returns Russian Post offices either by postal code or by coordinates, which distinguishes it from sibling tools like pochta_track (tracking) and pochta_tariff (pricing). However, it lacks an explicit verb like 'get' or 'find', making it slightly less direct than an ideal verb+resource formulation.

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 implies the tool is for looking up offices but provides no explicit guidance on when to prefer it over alternatives, nor any exclusions. It mentions two modes (postal code or coordinates) but does not explain when to choose one over the other or what happens if both are provided.

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