session_read_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It signals a read-only operation and describes the kind of content returned, but it does not explain authentication requirements, behavior on invalid or missing tabId, whether the page must be loaded, or any side effects. This is a meaningful gap.

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 that communicates the core purpose without filler or redundancy. Every part of the sentence adds useful information.

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?

While this is a relatively simple tool, there is no output schema and no parameter description, so the description must do more. It explains the high-level return content but leaves out how to select the tab and what the actual return structure looks like, making it incomplete for safe 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?

Schema description coverage is 0%, yet the description does not mention the sole tabId parameter at all. The agent is left to infer from the parameter name and type that it identifies a tab, but has no information about whether it is required, optional, or what value should be supplied.

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 clearly states the verb ('Read') and the resource ('full page content'), and enumerates the content types it returns: text, inputs, and interactive elements. It does not explicitly differentiate itself from siblings that may overlap, such as session_snapshot or session_evaluate, so it stops short of a 5.

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 no guidance on when to use this tool instead of session_snapshot, session_evaluate, or other siblings. The phrase 'authenticated page' hints at a precondition, but there is no explicit when-to-use, when-not-to-use, or alternative selection guidance.

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