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

With no annotations or output schema, the description carries the full behavioral burden, and it only partially does so: it enumerates returned artifacts, which is genuinely useful, but says nothing about whether the run must already exist, what happens for an unknown name, or whether any computation/simulation is triggered server-side. The reading "get" implies read-only, but that is inference rather than disclosure.

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?

One sentence fragment with no redundancy, but it is not front-loaded: it opens with the most obscure item ("the steps found in the video") and buries the core purpose. A leading clause such as "Returns the analysis for a named run, including ..." would fix both the structure and the missing verb.

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?

Because there is no output schema, the description must explain return values, and it does list the major content areas reasonably well. What is missing for a one-parameter retrieval tool is the identifier semantics and the lookup-failure behavior, plus any hint of how the run is selected relative to list_runs.

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 coverage is 0% for the single required parameter `name`, and the description never mentions it — it does not clarify whether `name` is a run name, a protocol name, a video identifier, or a human-readable label. The description therefore does nothing to compensate for the schema gap.

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 text is a noun phrase enumerating the payload contents (video steps with timestamps, open questions, simulator/protocol analysis, deck setup, runtime parameters, thermocycler minimum time) rather than a verb+resource statement. It conveys what a "run" record contains, but never says "retrieves the run record named X," so the agent must infer the action from the tool name alone.

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 when-to-use guidance and no mention of the siblings that overlap most directly, such as list_runs (to find a run) or get_protocol/get_receipt. The agent is left to guess whether this is a lookup, an analysis trigger, or a bundle of derived artifacts.

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