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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description adds useful context: the score is computed from Semantic Scholar publication counts using 90-day windows vs. baseline, is updated daily, and includes named output fields. No contradiction with annotations.

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?

Two dense but purposeful sentences front-load the return value and follow with precise when-to-use guidance, closing with update frequency. Every sentence earns its place and there is no 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?

For a read-only tool with one optional parameter and no output schema, the description names all returned fields, describes the methodology, and gives specific use-case timing. This is sufficient for an agent to select and invoke it correctly.

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 coverage for the single optional parameter 'days' is 100%, and the schema description already explains the history series, Gold tier requirement, and range. The tool description adds no additional parameter semantics, so the baseline of 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?

The description opens with a specific verb and resource: 'Returns a 0-100 frontier-hardware research-momentum score' and lists exact output fields. The topic (quantum computing, solid-state batteries, neuromorphic computing) clearly distinguishes it from the many opaque sibling tools, but no alternative tool is explicitly named.

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 call conditions: 'Call when the user asks about emerging-tech R&D acceleration, quantum/battery/neuromorphic research trends, or pre-patent signals, or when timing deep-tech investment, corporate R&D strategy, or technology-scouting decisions.' This is clear context, but it does not state when not to use it or name a sibling alternative.

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