session_console

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

The readOnlyHint annotation already signals a safe read operation. The description adds valuable behavior beyond the annotation: results are ordered newest last, backed by a 500-entry ring buffer, and capture output from page scripts, clicks, evals, and navigation alike. This gives the agent a solid mental model without contradicting 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 compact and front-loaded with the return format, followed by behavioral constraints and a practical usage hint. Both sentences earn their place, and there is no filler or repetition of schema facts.

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 a single required parameter, readOnlyHint present, and an explicit inline output schema, the description is complete for an agent to select and invoke the tool correctly. It also covers ordering, capacity, and capture scope, leaving no important gaps for this read-only diagnostic tool.

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% for the single session_id parameter, so the schema already documents that parameter. The description does not add extra parameter-level detail, but none is needed because the schema provides the meaning. Baseline 3 is appropriate.

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 names a specific verb ('Read'), a specific resource ('the session's recent page console output'), and includes the exact return shape. It is clearly distinct from sibling tools like session_network or session_state by focusing on console log/info/warn/error messages.

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 gives clear usage context: 'The fastest way to see WHY a page misbehaves: click the button, call this, read the error.' It implies this is the diagnostic tool for page misbehavior but does not explicitly mention when to prefer alternatives like session_network, so it stops short of a full when/when-not comparison.

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