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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description's job is to add operational context — and it does: results are ordered by newest registry update first, the default relevance floor is 1.8, and scope is restricted to aging-related trials. It does not mention pagination limits beyond what the cursor/limit schema already implies, so not a 5.

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-loaded with the use case, then scope, then return fields, then filters, then the sibling pointer. Every sentence carries information, though the middle catalog of fields is a slightly listy run-on rather than maximally tight.

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 no output schema, the description names the returned fields (phase, status, sponsor, size, conditions, interventions, latest change) and the ordering, and the schema handles pagination via cursor/limit. For a 9-parameter, 0-required read tool, nothing an agent needs to call it correctly 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 the enums, date format, limit bounds, and cursor mechanics are already fully documented. The description only restates the filterable axes in prose (words, phase, status, focus, industry, update date) without adding syntax or defaults beyond the schema; 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?

States a specific verb (lists) and resource (clinical trials bearing on human aging from ClinicalTrials.gov), and distinguishes itself from get_trial ("Read one with get_trial") and from generic trial registries ("Only trials about aging, not every registered trial"). An agent can route correctly without opening the schema.

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?

Gives concrete triggering user intents (what is recruiting, what changed lately, which trials test a drug, which companies run them) and names the exclusion plus the sibling to use for single-item retrieval. When-to-use and when-not-to-use are both explicit.

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