wet_lab_anchors

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

With no annotations, the description carries the full behavioral burden. It discloses useful conceptual traits: literature ranges are never point estimates, parameters come from fitting a noise-free oracle, and outputs are graded AGREE/NEAR/CONTRADICTED/UNANCHORED. However, it does not state whether the tool is read-only, whether it has side effects, or what the response structure looks like.

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 three dense sentences that front-load the tool's identity and role in the evidence chain. There is little waste, though the first sentence is syntactically heavy and could be clearer as a standalone purpose statement.

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 tool with no output schema and no annotations, the description should do more to explain what callers receive and how to interpret the grades. It covers the conceptual behavior and the comparison with the V&V chain, but it leaves the return structure and listing behavior largely to the schema.

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 100%, so the single optional 'key' parameter is already fully documented in the input schema. The description adds no additional meaning about the parameter or its accepted values, making the baseline 3 appropriate.

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 identifies the tool as the 'second evidence chain' dealing with literature ranges and implied parameters, which is a specific resource in this domain. It also distinguishes this chain from the V&V chain, but it never states a clear verb like 'retrieve' or 'list', leaving the exact operation slightly implicit.

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?

It gives clear context: read both the V&V chain and this chain, then gate on the more conservative one. That names an alternative evidence source and a decision rule, but it does not explicitly state when not to use this tool or how it relates to siblings like gate_decision.

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