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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint:false, so the safety profile is fully covered. The description adds useful context by naming ClinicalTrials.gov as the source and noting results are 'if available', but it does not address error behavior, availability, or other operational traits beyond the 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?

A single front-loaded sentence states the operation and key, then uses a compact list to specify the content categories without repeating the schema or annotations. Every clause adds information, and the source is included in a low-footprint parenthetical.

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 single-parameter read-only lookup with a documented output schema, the description is complete: it identifies the input key, the content scope, and the data source. Nothing essential for selecting or invoking the tool is missing.

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, the schema already fully documents the nct_id format and pattern. The description only says 'by NCT ID', which adds no meaning beyond the schema's parameter documentation, so the baseline 3 is appropriate.

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 identifies a specific verb and resource: returning full details for a single clinical trial keyed by NCT ID, and enumerates the content domains (protocol, conditions, interventions, eligibility, outcomes, sponsor, phase, design, dates, results). It does not explicitly distinguish itself from similarly named siblings such as clinicaltrials.trials.detail or health.clinical.search, so it stops short of 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 phrase 'Full details for a clinical trial by NCT ID' gives a clear context: use this when the agent already has an NCT ID and needs comprehensive trial information. It does not explicitly state when to prefer this over sibling search/stats tools or name alternatives, so there are no exclusions, but the intended trigger is clear.

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