validate_evidence_review

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool checks coverage, but does not explain what 'covers' means, whether the check is read-only, what criteria are used, how failures are reported, or what side effects may occur.

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?

The description is a single sentence with no filler, and the key verb and target are front-loaded. It is appropriately concise for the limited content it provides.

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?

Despite the presence of an output schema, the tool has two nested object parameters with no schema-level documentation and no annotations, yet the description offers only a high-level 'check coverage' statement. An agent would not know how to structure the inputs, interpret success, or understand the check's semantics in relation to surrounding research-validation tools.

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 the schema only lists 'review' and 'research' as generic objects with additionalProperties allowed. The description maps these names to conceptual meanings ('evidence review' and 'research artifact'), which adds a little value, but it does not explain expected fields, shapes, or constraints needed to call the tool correctly.

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 uses a clear verb ('Check') and names the specific resource ('independent evidence review') and target ('research artifact'), so the tool's core purpose is understandable. It does not explicitly distinguish itself from sibling 'validate_research_result', but its focus on review coverage is reasonably distinct.

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?

The description implies the tool is used when an independent evidence review exists and needs to be checked against a research artifact, but it gives no explicit guidance on when to choose this tool over siblings like validate_research_result or build_research_consensus. No exclusions, prerequisites, or alternative routing are provided.

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