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

With no annotations, the description does substantial work: it discloses that execution is simulation-only, that it runs analysis, deck configuration and play, that it returns the robot's report (status, command count), and that it takes about a minute the first time and is then cached. It does not say whether running affects persisted run state (e.g., writes a receipt) or what happens on failure, which is the main remaining gap for a mutation-like tool.

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?

Front-loaded with the core action and mode, and each subsequent sentence adds a distinct fact (return value, timing/caching, scope restriction). The middle clause ('the robot's analysis, deck configuration, play to the end') is a slightly listy restatement but still informative.

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?

The description covers purpose, execution mode, return shape, cost and scope, which is good for a tool with no annotations and no output schema. However, with 0% schema description coverage and an undocumented required 'name' parameter, an agent still lacks what it needs to fill in the arguments correctly.

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 carry parameter meaning and largely does not. 'Reactions' is mentioned but never explained (units, allowed range, effect on the run), and the required 'name' parameter is never referenced at all — the reader has to guess it is the run identifier.

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?

States a specific verb and resource ('Run the run's protocol.py end to end on Opentrons' own robot-server') plus the execution mode ('in Flex simulation'), which is clearly distinct from siblings like get_protocol or get_run that only retrieve data. An agent can tell immediately that this is the execute/validate step.

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?

Usage context is clear (end-to-end validation in simulation before real execution), and it gives an explicit scope exclusion: 'Runs only the protocol this server generated, never code an agent sends.' It does not name sibling alternatives or state when not to run it (e.g., after the protocol is known to be stale), so it falls short of full when/when-not routing.

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