fetch_strain

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

The annotations already disclose that this is not read-only, is open-world, and is non-destructive. The description adds useful context by saying it creates an immutable run and downloads a bounded official pair, but it does not explain permissions, side effects, or what "immutable run" entails. There is no contradiction with the annotations.

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 front-loaded sentence with no filler. Every phrase contributes to stating the action, resource, and side effect.

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 that downloads data and creates an immutable run, the description is too thin: it omits the event parameter, does not explain the resulting run, and provides no return-value context despite there being no output schema. The annotations cover some safety signals, but the description leaves important operational details unstated.

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?

The schema has one optional parameter, event, with a default, but schema description coverage is 0% and the description never mentions the parameter. No meaning is added beyond the bare schema property name.

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 uses a specific verb, "Download," and names the resource, "bounded official H1/L1 strain pair," plus the side effect of creating an immutable run. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as list_events or get_results.

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 versus alternatives, nor any stated prerequisites or exclusions. The only implied usage is that an agent should call it when it needs to download strain data and create a run.

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