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

With no annotations, the description carries the burden. It discloses the output categories (status, phase, top sponsors) but does not state whether the operation is read-only (implied by 'get'), whether condition matching is exact or partial, or what happens when no data matches. The word 'trends' is somewhat ambiguous since the described outputs are counts, not time-based trends, which introduces slight inconsistency.

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?

The description is compact and front-loaded: a one-sentence purpose, a one-sentence output explanation, and a practical example. No filler or redundancy; every sentence earns its place.

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?

Given the tool's relative simplicity, two parameters, and no output schema, the description covers the key aspects: what the tool returns (counts by status/phase/sponsor) and a representative usage scenario. It could be more complete by explicitly stating the output is aggregate statistics only (not individual trial data) and that it is a read-only operation, but the core information is present.

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 input schema already provides full descriptions for both parameters (condition and group_by) with 100% coverage. The description adds a few example values for condition and mentions the grouping dimensions (status, phase, sponsor) but does not significantly extend beyond the schema's own parameter documentation, so the baseline of 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 opens with a specific verb+resource: 'Get clinical trial statistics and trends for a condition.' It clearly distinguishes from siblings (search_trials, get_trial_details) by focusing on aggregate counts and trends rather than individual trial search or details. The example question further clarifies the tool's purpose.

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?

The description provides a concrete use-case example ('How many Alzheimer's trials are recruiting right now?') that signals when to use the tool for aggregate statistical questions. However, it does not explicitly mention when not to use it (e.g., for individual trial details) or directly reference alternatives, so it stops short of full exclusion guidance.

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