Clinicaltrials Get Study Results

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint. The description adds the critical context that results are only available when hasResults is true, and mentions the summary parameter impact on payload size. 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?

Two concise sentences that front-load the purpose and immediately follow with usage guidance. No redundant text; every sentence earns its place.

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?

Given the presence of an output schema (not shown but referenced), the description adequately covers purpose, usage, key behavioral constraints, and parameter guidance. It is complete for a fetch operation with good 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 coverage is 100%, but the description adds a usage tip: 'Use summary=true for large batches to avoid large payloads', which provides additional value beyond the schema descriptions. The sections parameter is well-documented in 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?

The description clearly states the verb 'Fetch' and the specific resource 'clinical trial results data' including outcome measures, adverse events, participant flow, and baseline characteristics. It also mentions the prerequisite condition 'only for studies where hasResults is true', which distinguishes it from sibling tools like clinicaltrials_search_studies that find studies.

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 instructs to 'use clinicaltrials_search_studies first to find studies with results', providing clear when-to-use guidance. Also implies the tool is for completed studies and those with results, helping the agent decide when to invoke this tool versus others.

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