get_zhnvlp_price

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

With no annotations provided, the description carries the behavioral burden. It discloses that this is informational ('Справка'), not medical advice, and that it is tied to the Pro tariff. For a simple read-only price lookup, this is reasonably transparent, though it does not detail error behavior when both optional params are absent.

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, compact sentence with the core result front-loaded first, followed by the lookup key and relevant caveats. No filler words are present.

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 is simple, the input schema is fully documented, and an output schema exists. The description gives the essential lookup semantics and important caveats. It could be slightly more complete by stating that at least one of name or MNN must be supplied, since both are schema-optional.

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 100%, so the baseline is 3. The description adds value by clarifying that the lookup works by either trade name or MNN ('по названию или МНН'), effectively describing the relationship between the two optional parameters beyond their individual schema descriptions.

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 the 'Предельная цена из реестра ЖНВЛП' (maximum price from the essential medicines register) and can be queried by name or INN. This distinguishes it from the sibling tools, which handle registration, cards, instructions, recalls, and general drug search.

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 usage: use this tool when you need a ЖНВЛП price by name or MNN. It does not explicitly state when to prefer it over search_drug or the other siblings, nor does it provide exclusions or alternative routing.

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