get_drug_card

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

No annotations provided, and the description does not disclose behavioral traits such as authorization needs, rate limits, or side effects. The 'Тариф Pro' phrase implies a paid tier but lacks clarity on restrictions. The list of fields is helpful but insufficient for a tool with no annotations.

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?

Description is a single sentence that efficiently conveys the tool's output and tariff. It is front-loaded but includes a minor marketing component ('Тариф Pro'). No wasted words aside from that.

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?

Output schema exists (not shown), so return values are covered. However, with no annotations, the description lacks context on prerequisites, error handling, and access restrictions. The tool's special tariff suggests additional context is needed.

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 both parameters (name, ru_number) described. The description adds context about the output fields but does not enhance parameter semantics beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states the tool provides a 'reference card' of a drug from GRLS, listing specific data fields (trade name, INN, forms, dosages, etc.). It distinguishes from siblings like search_drug (generic search) and get_zhnvlp_price (pricing) by specifying a comprehensive 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?

No explicit guidance on when to use this tool versus alternatives. The mention of 'Тариф Pro' hints at a paid requirement but does not state usage context or exclusions. No comparison to sibling tools like check_drug_registration or search_drug.

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