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

Annotations only declare readOnlyHint and openWorldHint, but the description adds the two things an agent actually needs before calling: a per-call price ($0.002 USDC via x402 on Base/Solana/Arc) with the guarantee that failed calls are not charged, and a data-provenance warning that results are sponsor-registered and unverified.

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?

Purpose, returned fields, provenance caveat and price are packed into three front-loaded sentences with no filler. The field enumeration borders on duplicating the existing output schema, which is the only minor waste.

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?

With annotations covering read-only/open-world behavior, a full schema, and an output schema, the description covers the remaining critical gaps: cost, payment mechanism, failure billing, and data reliability. It stops short of describing result ordering or pagination, but nothing essential for 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?

Schema description coverage is 100%, so both parameters are already documented in structured data. The description's restatement of 'condition, drug or keyword' loosely maps to q but adds no character-range or limit/ranking semantics beyond the schema, so the baseline of 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 names the exact resource (ClinicalTrials.gov studies) and the query axis (condition, drug or keyword), then enumerates the returned fields. That distinguishes it from generic health directories in the sibling list, though it never names a specific sibling or alternative source to contrast with.

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 implied by 'matching a condition, drug or keyword,' so an agent can infer the search intent, and the 'Registry records only' caveat signals when results may not be authoritative. However, it gives no explicit when-to-use/when-not guidance versus adjacent tools like gov_openfda_drugsfda or gov_npi_registry.

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