Get browser session

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no contradiction. The description adds a clarifying note about session names being workflow labels rather than internal agents, which is useful context but not behavioral detail beyond what annotations cover. It does not describe output or side effects, but those are trivial for a read-only tool.

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 two sentences with no fluff. The first sentence states the core purpose, and the second adds a semantic clarification. Each sentence earns its place, and it is well-structured.

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?

The tool is simple with one parameter and an output schema that likely defines return format. The description fails to provide guidance on obtaining sessionId or connections to other session tools, but given low complexity and existing output schema, it is not critically incomplete. However, it could mention using browser_session_list to discover valid IDs.

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?

With schema description coverage at 0%, the description must compensate for the undocumented sessionId parameter. It only indicates 'explicitly addressed' without explaining what sessionId is, its format, or how to obtain it. This adds minimal meaning beyond the parameter name.

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 states specifically that the tool inspects one explicitly addressed browser session, with the verb 'Inspect' and a clear resource. It distinguishes from sibling tools like browser_session_list (which lists all) and create/close tools by emphasizing 'explicitly addressed'.

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 explicit guidance on when to use this tool versus alternatives. It does not mention browser_session_list for finding session IDs or any prerequisites. The 'explicitly addressed' phrase implies an ID is needed but does not direct the agent on how to obtain it.

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