websex_browser_get

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

No annotations exist, so the description carries the full disclosure burden. 'Inspect' plus 'live session' implies a read-only lookup, and it names the returned fields, but there is no statement about side effects, authentication/engagement scoping, or whether the session must already exist.

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 the verb and scope first and no filler. Slight redundancy in listing return fields that an output schema already covers, but nothing wasteful.

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 explaining return values is unnecessary. However, for a tool requiring two undocumented identifiers, the description supplies no parameter meaning and no behavioral context to compensate for the absent annotations.

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% for two required parameters (engagement_id, session_id), and the description never mentions either one. It does not explain the engagement/session identifier pairing or compensating syntax that would make up for the schema gap.

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 (inspect), resource (one live browser session), and enumerates what is surfaced (URL, title, network event count, interception rules). The word 'one' distinguishes it from websex_browser_list, but it does not disambiguate from websex_browser_state, which sounds like an overlapping read of the same session.

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?

No when-to-use, when-not-to-use, or alternative is named, despite obvious candidates among siblings (websex_browser_list to enumerate sessions, websex_browser_state or websex_browser_snapshot for state). The only guidance is the implied 'one' vs many contrast.

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