websex_browser_state

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

With no annotations, the description carries the full burden. The verb 'Read' does imply a non-mutating operation and 'live browser session' hints that an active session must exist, which is meaningful context. However it says nothing about permissions, failure modes when the session is inactive, or volume/limits of the returned data.

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?

A single front-loaded sentence with zero filler; the action and the exact resources read come first. Nothing in the sentence is redundant.

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?

An output schema exists, so return-value explanation is legitimately absent. But with 0% parameter coverage and no annotations, the definition still leaves required parameters and session preconditions unexplained, making it only minimally complete for an agent to invoke it 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% and the description never mentions the two required parameters (engagement_id, session_id) or their format/relationship. The phrase 'live browser session' loosely gestures at session_id, but neither identifier's meaning or expected value is clarified.

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 gives a specific verb ('Read') and an explicit resource set ('cookies, localStorage, and sessionStorage'), scoped to 'a live browser session'. That clearly separates it from the obvious sibling websex_browser_set_state (which writes the same state) and from websex_browser_snapshot/evaluate, without needing to name them.

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?

There is no when-to-use guidance, no statement of alternatives (e.g., 'use instead of browser_evaluate for reading storage'), and no prerequisites such as requiring an already-created/navigated session. The reader must infer usage entirely from the purpose sentence.

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