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

Annotations already declare the safe-read profile (readOnlyHint, idempotentHint, non-destructive, openWorld), so the bar is lower. The description still adds real context beyond structured fields: it states the cost model ('free within the daily allowance, then $0.003 USDC per call via x402') and that results include matching trial sites, which is uncommon and agent-relevant.

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 tight sentences with the purpose front-loaded and the pricing clause placed second. Nothing is redundant, though the x402 payment detail is somewhat tangential to selection and could be trimmed.

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 an output schema present, return values need not be described, and annotations carry the safety profile. The description covers purpose, scope, and cost, leaving only minor gaps such as how 'near a place' is bounded (radius/proximity) and pagination behavior, both of which are partly covered by the page_token parameter.

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 schema already documents all four parameters (limit, location, condition, page_token). The description only echoes 'a condition in a city, region or country' matching the location/condition params and adds no syntax, format, or range detail, so 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 names a specific resource and scope: 'Studies recruiting (or about to) for a condition in a city, region or country, with the matching trial sites.' The 'recruiting' status filter plus 'near a place' implicitly separates it from clinical-trials__search/stats/study, but it never names an alternative explicitly, so differentiation is inferred rather than stated.

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 by the resource framing (recruiting trials near a place). There is no explicit when-to-use/when-not, no prerequisites, and no routing to clinical-trials__search for non-recruiting lookups, so an agent must infer the boundary from the tool name.

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