neuron_start_replay

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

No annotations are provided, so the description carries the full burden. It discloses that recorded steps are re-executed on the current tab, but it omits important behavioral context: this likely mutates page state, may run asynchronously, and may need to be monitored or stopped. There is no mention of completion, failure, or side-effect scope.

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. The dash-definition explains the action efficiently and every phrase contributes meaning.

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 re-executes a workflow on the live page, with no annotations, no output schema, and only one parameter, the description is too thin. It lacks guidance on async behavior, how to check workflow status, how to stop replay, and what the agent should expect after invocation.

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 input schema already documents workflowId with 100% coverage, and the description itself adds no parameter-level detail beyond what the schema provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a specific verb ('Replay') and resource ('saved workflow'), and adds the scope 'on the current tab.' This makes it clearly distinct from related tools like neuron_start_recording, neuron_stop_replay, or neuron_run_sequence without needing to open the schema.

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?

The description provides clear context: use this when you need to replay a saved workflow, and the replay executes against the current tab. However, it does not name alternative tools or mention exclusions such as requiring a recording to exist or using workflow_status to check progress.

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