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

Annotations already establish readOnly, idempotent, non-destructive and a closed corpus (openWorldHint=false). The description adds the genuinely non-obvious behavioral fact that results are capped at 5 pages and that each result carries title, date, link and summary, which annotations cannot express.

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 sentences, no filler: the corpus scope comes first and the result shape second. Every clause carries information an agent can act on.

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 one-parameter search with no output schema, the description covers the corpus, the hard result cap and the return fields, so an agent can call and interpret it. It stops short of explaining ranking or how to retrieve results beyond the first five.

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% and the single query parameter is documented in the schema with concrete examples ('PUE benchmarks', 'fibre latency London Frankfurt'). The description adds no syntax, quoting or format guidance beyond that, so the 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?

The description names a specific verb (search) and a scoped resource (ScienceShot's trackers, reference pages, articles) and even enumerates the topical domains covered. That makes it immediately distinguishable from siblings like data_centre_market_overview or grid_connection_status, which are specific lookups rather than general search.

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?

Usage is only implied: an agent can infer this is the fallback for free-text discovery when no specific sibling lookup applies, but the description never states that. There are no when-not conditions or explicit routing to the sibling tools.

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