get_browser_session

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

With no annotations, the description carries the full burden, but it does disclose two useful traits beyond the schema: the connectUrl is freshly signed (not cached) and it is only returned 'while the session is running', hinting at a failure condition. It omits auth/permission requirements and any rate-limit or error behavior for stopped/expired sessions.

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?

Two short sentences with zero filler; the core action is front-loaded and the return-value note follows immediately. Every sentence earns its place.

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?

There is no output schema, so the description must hint at returns, and it does identify the key payload (connectUrl) plus the running-session precondition. The undefined term 'state' leaves the full response shape somewhat ambiguous, but for a one-parameter getter this is close to complete.

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?

Only one parameter (sessionId) and schema coverage is 100%, so the schema already documents its format and UUID pattern. The description adds no meaning beyond that, which matches the baseline 3 for fully documented schemas.

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 and resource ('Get a Cloud Browser session's state'), which clearly separates it from list_browser_sessions, create_browser_session, and stop_browser_session. It does not, however, explicitly name a sibling or state that it operates on a single session by id, so differentiation is inferable rather than stated.

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 mention of returning a connectUrl implies the use case (retrieving an attachment URL for a running session), but there is no explicit when-to-use guidance, no prerequisites, and no named alternative such as list_browser_sessions. Usage is implied rather than spelled out.

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