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

Annotations already indicate readOnlyHint=true, so no contradiction. The description adds valuable behavioral context beyond annotations: the score is a composite z-score, weekly since 2000, and includes top_drivers, percentile, and methodology_version. It does not over-explain trivialities, but it could also mention the optional history behavior (Gold tier) which is left to the schema, so a 4 is appropriate.

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 well-structured and efficient. The first sentence delivers the core functionality, the second provides usage context, and the third is a brief update frequency note. Every sentence earns its place, with no redundancy or filler, making it easy for an agent to parse quickly.

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?

The description is complete for a read-only tool with no output schema. It explains the main return components (top_drivers, percentile, methodology_version) and gives clear use cases. The only missing piece is a more explicit description of the default snapshot vs. the optional history series, but the schema covers that. Given the tool's moderate complexity, this is sufficiently complete.

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% for the single 'days' parameter, which already describes its purpose, range, and Gold tier requirement. The tool description does not add any extra meaning about the parameter; it only implies the default snapshot behavior through the primary return description. This meets the baseline of 3 but does not exceed it.

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 is highly specific: 'Returns a 0-100 US clinical-trial pipeline activity score' with a detailed definition of the composite z-score and its components (active trial volume, phase distribution, registration momentum). It clearly communicates the tool's unique output, distinguishing it from any sibling tools through its precise resource and metrics.

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?

It provides explicit when-to-use guidance: 'Call when the user asks about clinical trials, drug development pipelines, biotech or pharma R&D activity, or when timing biotech sector-rotation or investment-screening decisions.' However, it does not mention when not to use the tool or name any alternative sibling tools, so it falls short of a 5.

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