clinical_trials_stats

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

Mentions parallel queries for 8 statuses, providing behavioral insight beyond the readOnlyHint annotation. No contradiction with annotations.

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?

Three focused sentences: purpose, output detail, and usage examples. No unnecessary words.

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?

Covers all key aspects: input (condition or drug), output (counts by status), and behavioral trait (parallel queries). Sufficient for user understanding given well-described schema and annotations.

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 already provides 100% description coverage for both parameters (condition and search_as_drug). Description reinforces usage but adds minimal new semantic detail beyond the schema.

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?

Description clearly states it provides trial count breakdown by recruitment status for a condition or drug/intervention, distinguishing it from clinical_trials_search (individual trials) and clinical_trials_detail (specific trial details).

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?

Explicitly states it works for both diseases and drug names with examples ('breast cancer', 'semaglutide'), implying when to use. Does not explicitly state when not to use or name alternatives, but context is clear from sibling tools.

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