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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety and idempotency profile is covered. The description adds the scoping fact that results are 'normalized public' entities, which is meaningful context beyond annotations. It does not disclose result format, pagination, or scoring, but the annotation coverage lowers the burden.

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?

One short sentence, front-loaded with the verb, which is structurally fine. But it is under-specified rather than concise – the brevity comes at the cost of needed information rather than from removing waste.

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 search tool with 0% schema description coverage and no output schema, an agent needs to know query semantics and result shape. The description supplies neither, and gives no differentiation across three sibling search tools. Incomplete relative to the tool's complexity.

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%, so the description must compensate, and it does not. Neither 'query' (the matching semantics – exact, prefix, full-text?) nor 'limit' (default 20, max 50, pagination behavior) are explained anywhere. This is a real gap for a search tool where query semantics determine correctness.

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?

States a verb (Search) and resource (normalized public evidence entities), which is more specific than a tautology. However, the sibling set contains evidence_search, evidence_semantic_search, and evidence_universal_search, and the description offers no differentiation from any of them. An agent cannot tell which search tool to pick.

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?

No when-to-use guidance and no mention of the three closely-named search siblings. The description gives no condition that would route an agent to this tool over evidence_search or evidence_semantic_search.

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