get_drug_info

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

With no annotations, the description adds behavioral context via the agent contract (use structuredContent as truth, preserve fields). This aids correct usage, though it omits details like auth needs or rate limits.

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 two sentences; the first is clear and informative, the second adds behavioral guidance. It is reasonably concise, though the second sentence could be integrated more smoothly.

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 no annotations and many sibling tools, the description distinguishes its comprehensive scope well. It mentions preserving fields, but lacks detail on error handling or edge cases. Output schema is referenced, so return values are covered.

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 67% (2 of 3 params described). The description does not elaborate on parameters beyond the schema. Since coverage is high, baseline is 3; no additional value is added.

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 'Get comprehensive information about a drug including indications, dosage, warnings, and pharmacology.' This specific verb+resource+scope differentiates it from sibling tools like `get_drug_dosage` or `get_drug_warnings`, which cover only subsets.

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 includes an 'Agent contract' but does not explicitly state when to use this tool versus alternatives. It implies comprehensive info, but lacks explicit when-not conditions or alternative recommendations.

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