validate_research_result

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It discloses that the operation is 'deterministic' and acts as a 'gate,' but it does not explain whether validation failures block execution, whether the tool has side effects, what permissions are needed, or how results are returned. This is comparable to a mutation tool that never states its effects.

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 front-loads the core action. The phrasing 'deterministic scope/policy gate' is jargon-heavy but compact and arguably earns its place by hinting at the validation rule type.

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?

Given two opaque nested parameters, no annotations, and no parameter documentation, the description is not complete enough for confident invocation. The existence of an output schema reduces the need to describe return values, but the description still leaves the input contract and gate semantics unexplained.

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 description does not compensate. It does not explain that 'research' is the artifact being validated or that 'request' carries the scope/policy context. Both parameters are opaque nested objects with additionalProperties true, so the agent has no semantic anchor for what to provide.

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 names a specific action ('Run') and a specific resource ('one research artifact'), and 'deterministic scope/policy gate' conveys a clear validation function. It does not explicitly differentiate from sibling tools like validate_evidence_review, but it is not tautological and is more specific than a vague summary.

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 gives no guidance on when to use this tool versus validate_evidence_review, validate_prompt, or other sibling validators. There is no mention of prerequisites, intended workflow position, or exclusion criteria. The only contextual hint is 'over one research artifact,' which is a scope statement rather than usage guidance.

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