validate_reference

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

No annotations, so the description carries the full behavioral burden, and it discloses almost nothing: not what validation performs, what a failure looks like, whether provenance hashes are checked, or whether evidence is mutated. The one scope remark ("without literature claims") is a faint behavioral hint but is contradicted in spirit by the optional literature input.

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 no padding, which is structurally good, but its brevity comes from under-specification rather than discipline, and the final clause muddies rather than sharpens the scope.

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 9-parameter validation tool with zero annotations, an output schema (returns covered) and 0% schema description coverage, the description is drastically incomplete. An agent cannot infer which inputs are required in practice, how the literature and DFT evidence interact, or what constitutes a valid invocation.

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?

Nine top-level parameters with 0% schema description coverage, and the description adds no parameter meaning whatsoever — it never mentions literature records, dft_provenance, or any of the four barrier values. The nested $defs descriptions live in the schema, not the description, so nothing compensates for the coverage gap.

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+resource ("validate barriers against supplied DFT/reference evidence"), which is more than a tautology, but the trailing clause "without literature claims" is ambiguous and sits awkwardly beside a schema that accepts a `literature` array. No differentiation from siblings like verify_dft_dataset or compare_models.

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, no prerequisites, no named alternatives among the seven sibling tools. The only usage-ish hint is the exclusionary phrase "without literature claims," which is left unexplained and is not framed as a selection condition.

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