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

No annotations are provided, so the description must carry the behavioral burden. It does well by disclosing the matching precedence (slug, exact name/brand, substring) and what the returned record contains (efficacy figures with estimand tags, page URL), though it omits what happens when no drug matches or when matching is ambiguous.

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 front-loaded with the core purpose, then adds only the matching behavior needed to invoke the tool correctly. Both paragraphs are dense with useful information and contain no filler.

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 one-parameter lookup with no output schema, the description is largely complete: it explains matching and mentions key returned fields. It still lacks explicit not-found or ambiguity behavior, which would help an agent understand failure modes.

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 explain the single 'name' parameter. It does so thoroughly, specifying that input can be a slug, exact name/brand, or substring, and gives concrete examples that clarify accepted forms.

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 states a specific resource and scope: the full record for one drug, including efficacy figures and page URL. That distinguishes it from sibling tools like search_drugs or compare_efficacy, which cover multiple drugs or comparisons.

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?

Usage is implied by 'one drug' and the matching behavior, suggesting direct lookup rather than search. However, it does not explicitly say when to use this instead of search_drugs or other siblings, nor when not to use it.

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