validate_evidence_assessment

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

With no annotations, the description carries the full burden and does meaningfully disclose behavior: every attempt is persisted regardless of outcome, and passes are only structurally admissible proposals rather than semantic judgments. The NE edge case tied to a server-derived MissingnessRecord is a real behavioral detail. Gaps remain on permissions, idempotency, and failure behavior.

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?

Three short sentences with the core action front-loaded and no padding. The jargon ('structurally admissible', 'MissingnessRecord') is domain-specific rather than wasteful, though the all-caps emphasis adds little structural value.

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?

An output schema exists so return values need not be explained, which the description correctly omits. However, with zero annotations and zero field descriptions, the definition is thin on permission requirements, error semantics, and the meaning of most parameters for a stateful persist operation.

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 only partially does, explaining the special 'NE' status binding. The required fields (item_id, claim, proposed_status) and the optional conditions/evidence_ids/model_reported_confidence carry no explanation in either place, though most names are self-evident.

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 states a specific verb pair (validate, persist) and a scope (structural admissibility), and explicitly bounds itself as NOT a semantic adjudicator. Combined with the tool name, an agent can tell this is a validation-and-record step. It does not, however, name or distinguish itself from any sibling tool.

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 explicit when-to-use or when-not-to-use guidance and no named alternative among list_sources, find_evidence, run_document_review, or build_evidence_matrix. The clause 'it does not semantically adjudicate the claim' hints at a boundary but never tells the agent when to call this versus a semantic check.

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