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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, which covers the safety profile fully. The description adds no behavioral context beyond that — no result ordering, coverage limits, pagination behavior, or auth requirements — so it earns little credit against the already-rich 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?

A single front-loaded sentence with zero filler and the search verb stated immediately. It is efficient, though arguably too terse for a tool with a 50-result cap and no sibling disambiguation.

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 2-parameter search tool with no output schema, the description omits output shape, pagination/cap behavior, and any distinction from the three nearby search siblings. It is incomplete relative to what an agent needs to pick and call 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 description coverage is 0% and both parameters are undocumented: the 300-character query cap and the 1-50 limit/default 20 range are nowhere explained. The description adds no parameter meaning beyond what the raw schema types convey, leaving the limit semantics and query scope unexplained.

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 gives a specific verb ('Search') and enumerates the resource scope (public evidence, editorial, news, newsletter, forum records), so an agent knows what it queries. However, it never explains what makes it 'universal' versus the sibling evidence_search or evidence_semantic_search, so differentiation is absent.

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?

There is no when-to-use guidance, no conditions or exclusions, and no mention of alternatives despite close siblings (evidence_search, evidence_semantic_search, evidence_search_entities) that an agent must choose between. Usage must be inferred entirely from the name.

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