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

Annotations declare readOnlyHint=true, and the description adds behavioral context beyond that by explaining the score's rolling-window computation, the baseline comparison, and the daily update frequency. It does not introduce any contradictions and provides meaningful methodological detail.

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 two sentences, front-loaded with the primary output and calculation, followed by explicit usage cases and update frequency. Every sentence contributes meaningful information without redundancy or filler.

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?

Despite lacking an output schema, the description lists the key output fields (trend, z_score, recent_window_count, baseline_window_mean, baseline_window_std, per_variant_w0, window_counts) and explains the baseline concept. It provides enough context for an agent to select and invoke the tool, though it does not detail the exact format or interpretation of every field.

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 provides 100% coverage for the single 'days' parameter, including its optionality, range, output behavior, and tier requirement. The description itself does not mention the parameter, so it adds no additional semantic value; however, since the schema fully documents it, a baseline score 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 ('Returns') and clearly defines the resource ('biotech preprint-velocity score') and its calculation (rolling 90-day bioRxiv count vs 8 trailing 90-day windows). It distinguishes itself from the many sibling tools by focusing on biotech preprint acceleration and listing distinct output fields.

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 explicit call scenarios: 'Call when the user asks whether life-science R&D output or new-biology preprint flow is accelerating, or when timing pharma horizon-scanning, biotech investment, or research-intelligence decisions against a trailing 2-year baseline.' This gives clear context for use, but does not mention exclusions or alternative tools, so it is a 4 rather than 5.

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