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

Annotations only supply readOnlyHint/openWorldHint; the description carries the rest of the burden, explaining how to interpret the degraded flag and stale sync timestamps and what obligation follows ('label it partial'). With no output schema, enumerating the returned fields is genuinely additive rather than redundant.

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?

Front-loads the hard constraint, then payload, then interpretation rule, then next steps — a logical progression with no filler sentences. It is dense and the caps-lock directive is slightly shouty, but every clause does work.

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 zero-param, no-output-schema tool with thin annotations, the description supplies everything an agent needs: what comes back, how to read the freshness/degradation signals, and which tools to chain into. No material gap remains.

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?

The tool takes zero parameters, so the schema has nothing to document and the baseline is 4. The description correctly does not invent parameter guidance for a parameterless call.

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?

States a specific verb and resource ('Returns every upstream registry') and immediately enumerates the payload fields (base URL, API type, licence, record count, last sync, degraded flag, schema-contract verdict). It also distinguishes itself from the lookalike siblings get_trial_stats and search_world_trials by name.

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?

Explicit when-to-use is front-loaded in caps ('USE BEFORE PRESENTING TRIAL EVIDENCE AS CURRENT OR WORLDWIDE'), and a NEXT clause names both follow-on tools plus the exact condition for choosing search_world_trials with an explicit `registry`.

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