browse_session_action

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

Annotations already indicate readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds almost no behavioral context beyond 'bounded', which is too vague. It does not disclose that actions may navigate, evaluate JavaScript, modify page state, or perform irreversible interactions, leaving significant risk unaddressed.

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 sentence with zero wasted words, front-loading the core purpose effectively. However, given the tool's complexity (large action union, many options), a bit more orientation would be appropriate; it is slightly under-sized rather than ideally concise.

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 rich schema, annotations, and an output schema, the description is minimally viable. It states the core function and existing-session requirement. However, it lacks usage context, does not clarify the variety of supported actions, and offers no differentiation from siblings, making it incomplete for a tool of this complexity.

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?

The schema description coverage is 100%, and the input schema provides detailed descriptions for parameters like sessionId, action, captchaPolicy, and snapshot limits. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 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 'Run one bounded action in an existing browser session' uses a specific verb ('run'), a clear resource ('bounded action'), and context ('existing browser session'). It effectively distinguishes this from siblings like browse_session_start (create) and browse_sequence (multiple actions) by emphasizing 'one bounded action'.

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 provides no guidance on when to use this tool versus alternatives such as browse_sequence or browse_session_navigate. It implies a precondition (existing session) but does not state exclusions, alternatives, or when a different tool would be more appropriate.

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