assemble_target_disease_evidence

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

No annotations are provided, so the description carries the full behavioral burden. It usefully indicates that the tool replays frozen evidence and returns typed missingness, implying a deterministic read-oriented operation, but it does not disclose permissions, side effects, rate limits, or whether any state changes.

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 two tightly written sentences with no filler. The action and scope are front-loaded, and the return behavior is stated immediately after, so every sentence earns its place.

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 in depth. However, with no annotations and 0% schema description coverage, the description leaves key calling context missing: it does not explain parameter semantics, usage relative to the sibling, or the operational meaning of "scoped records" and "typed missingness."

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. It offers concrete values (NOD2/TNF for target, IBD for disease), which adds some meaning beyond the bare schema, but it does not explicitly map these to the parameters or clarify whether they are examples, allowed values, or required formats.

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 an action ("Replay") and a resource ("frozen evidence") scoped to NOD2/TNF and IBD, so the general intent is inferable. However, "replay frozen evidence" is jargon-heavy and does not clearly state that it assembles evidence for an arbitrary target/disease pair, nor does it distinguish this tool from validate_dossier_references.

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 guidance on when to use this tool, when not to use it, or how it relates to the sibling validate_dossier_references. The description supplies context but no selection criteria.

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