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

Annotations already establish the safe read-only, idempotent profile, and the description layers on genuinely new behavioral facts: element-scoped steps arrive with an empty body and an opaque id that this tool resolves back to the findElement locator, and networkDuring explicitly reports when no traffic was captured rather than returning a misleading empty list.

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 purpose and dense with useful detail, but the em-dash-heavy sentences run long and the element-resolution explanation could be tightened. Every sentence does earn its place, so it stops short of waste.

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly: bodies, status, timing, resolved locator, and correlated network requests. An agent has everything needed to call and interpret the result.

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 all three parameters (sessionId, index, includeNetwork) are already documented in the schema, including the index semantics and the default-true network flag. The description adds only marginal semantics, mainly the browser-only scope of network correlation, so the baseline of 3 applies.

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 ('Open ONE step of a run') and enumerates exactly what is returned: request body, response body, status, timing, and the resolved locator. It is immediately distinguishable from automation_session_commands, which it names as the source of the index.

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?

Explicitly prescribes the workflow: 'Use automation_session_commands first to get the step index, then come here for the step that matters.' It also states when the tool is the right answer ('which element?') and scopes the network behavior to browser runs only.

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