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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations lack: the pricing/rate model (free within a daily allowance, then $0.002 USDC per call via x402). It does not say what happens on an invalid or unknown NCT number, which is the main remaining gap.

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 dense, front-loaded sentence: scope first ('One study'), then payload fields, then the commercial/pricing clause. No wasted sentences, though the long comma-separated field list is slightly list-like and the pricing tail is appended somewhat abruptly.

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 ID parameter) and an output schema exists, so return values need not be explained — yet most of the description's word budget goes to enumerating returned fields, which the output schema already carries. For a complete picture an agent would still want to know error behavior for invalid/withdrawn NCT IDs and confirmation that the call is a single-record lookup; the pricing disclosure is the main compensating value.

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 description coverage is 100%, so the sole parameter nct_id is documented structurally, and the schema's own text ('NCT number') is thin enough that the description's mention of the NCT number is not redundant filler. Still, the description adds no format detail (e.g., 'NCT' + 8 digits) or validation behavior, so baseline 3 applies.

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 opens with 'One study' and enumerates exactly what the record contains (title, status, phase, conditions, interventions, sponsor, enrolment, dates, eligibility, outcomes, countries, results-posted flag), which distinguishes it from sibling list/search tools like clinical-trials__search and clinical-trials__recruiting. The retrieval verb ('fetch'/'return') is left implicit, but the resource and scope are unambiguous.

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?

Usage is only implied: 'One study ... NCT number' suggests lookup-by-identifier rather than browsing, which routes an agent away from search/recruiting. However, no explicit when-to-use statement, no named alternative, and no guidance on prerequisites (e.g., needing a valid NCT ID or what to do if unknown) are given.

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