get_zhnvlp_price

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

With no annotations provided, the description carries the full burden. It explains the tool's function (checking list inclusion and returning price) but does not disclose any behavioral traits such as destructive actions, rate limits, or authentication needs. The mention of 'Тариф Pro' hints at a paid tariff but lacks explicit detail.

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 extremely concise: two sentences. The first clearly states the purpose, and the second specifies the input options and tariff. No wasted words.

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 lookup tool with an existing output schema, the description is adequate. It covers the core functionality. However, it could briefly mention how to interpret the output or any constraints (e.g., mutual exclusivity of parameters) for completeness.

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% with descriptions for both parameters. The description adds the hint 'Задайте name или mnn', implying mutual exclusivity, which goes beyond the schema. This provides useful usage guidance.

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 checks if a drug is in the ЖНВЛП (essential drugs list) and returns the registered price (ПЗЦ) by form/dosage/packaging. It specifies the required input (name or mnn), distinguishing it from sibling tools like check_drug_registration or get_drug_card.

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 tells the user to provide name or mnn but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites like required permissions. Usage is implied but not fully guided.

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