drug_trials

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

Annotations already declare readOnlyHint=true, so safety is covered and the bar is lower. Beyond that the description adds nothing: no indication of return shape, result volume, pagination, or what identifier namespaces the drug must come from (e.g., must it match drug_search output).

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?

One short, front-loaded clause with zero waste. It is efficient but borders on under-specification for a tool that has several look-alike siblings, so not a full 5.

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 param, read-only, no output schema), so little is needed, and the annotation plus schema cover the mechanics. Still missing is any hint of what the returned trials contain or how results are bounded, which an agent would want before calling.

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?

A single parameter with 100% schema description coverage, so the schema already carries the semantics; the description's 'for a drug' merely restates it. Baseline 3 applies since the schema does the heavy lifting and the description adds no format or naming guidance.

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 (find) and resource (clinical trials) scoped to a drug, so the agent knows exactly what it retrieves. It does not differentiate from close siblings like gene_trials, disease_trials, variant_trials, or trial_search, leaving the agent to infer the distinction from parameter shape alone.

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 'for a drug' phrasing implies the use case (you have a drug identifier and want trials), but there are no explicit when-to-use rules, no named alternatives, and no exclusions against the four trial-adjacent siblings in the toolset.

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