Drugbank Search

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the authentication requirement and where to obtain a key, but says nothing about rate limits, failure modes, or result shape (partially mitigated by the existing output schema).

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?

Two short sentences, purpose front-loaded and the prerequisite second. No filler or repetition of the schema. It is efficient, though not maximally information-dense for its length.

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 two-parameter search tool with full schema coverage and an output schema, the definition covers purpose and the one non-obvious operational requirement (API key). The missing piece is sibling routing among the many drug/pubmed tools, which is a genuine but not fatal gap.

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?

With 100% schema description coverage on both parameters, the schema already documents the query format ('metformin', 'aspirin') and the max_results range (1-50). The description adds no syntax, matching, or defaulting detail beyond that, so the baseline 3 applies.

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?

States a specific verb (search) and resource (DrugBank) and enumerates what the results cover (targets, enzymes, interactions), which implicitly differentiates it from the openFDA drug siblings. It stops short of explicitly naming which sibling to use for which drug-information need, so it lands at a strong 4 rather than a 5.

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 gives a setup prerequisite (DRUGBANK_API_KEY env var with a signup link) but no guidance on when to choose this over openfda_drug_label, openfda_adverse_events, or pubmed_search. The agent must infer the selection context entirely from the tool name.

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