get_drug_warnings

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful context about the content (regulatory warnings, withdrawals, boxed labels) but does not disclose any additional behavioral traits such as error handling, availability, or rate limits. With annotations lowering the bar, this is adequate but not rich.

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 a single, front-loaded sentence that states the core function without any filler. Every word contributes to understanding the tool's purpose.

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?

The tool is simple (one required parameter, read-only, has output schema), and the description captures its purpose. However, it lacks parameter semantics and usage guidance, which are important for an agent to correctly invoke it. The output schema and annotation cover some gaps, but the missing param explanation leaves it incomplete.

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?

The input schema defines a single required parameter (chembl_id) with no description, and the tool description omits any explanation of what this identifier is or how it should be formatted. With 0% schema description coverage, this is a significant gap that the description fails to fill.

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 uses a specific verb ('Fetch') and clearly identifies the resource ('detailed regulatory warnings') with illustrative examples ('withdrawals and boxed labels'). This distinguishes it from sibling tools like get_drug_adverse_events or get_drug_pharmacovigilance, which cover related but distinct safety data.

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 provides no guidance on when to use this tool over similar drug-related tools. It does not mention alternatives, exclusions, or scenarios, leaving the agent to infer its use case from the name alone.

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