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

The annotations already establish read-only, idempotent, closed-world and non-destructive behavior, so the description's added value is the result contract: a hard cap of 5 pages and the fields returned (title, date, link, summary). That cap is meaningful behavioral context an agent cannot get from the annotations, and there is no output schema to cover it.

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. Purpose comes first, return shape second, and every clause carries information (topics, cap, fields).

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 read-only search with full annotation coverage, the description supplies the subject domain and the return contract, which is enough to invoke it correctly. The only remaining gap is relative positioning against the sixteen sibling tools, none of which are named.

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?

There is a single required parameter at 100% schema description coverage, including two concrete example queries, so the schema already does the semantic work. The description adds nothing about query syntax, matching behavior, or how to phrase searches for better recall, which is the baseline expectation here.

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 resource ("ScienceShot's science reference pages and articles") and bounds the topical scope to radiation/particle physics, photonics, electronics and quantum physics. That scope implicitly separates it from the sibling calculators, though it never explicitly contrasts itself with them.

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 for retrieving reference literature on the listed topics rather than computing values. There is no explicit statement of when to prefer this over the many domain-specific sibling tools, and no exclusions or prerequisites.

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