Check Session Health

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

Annotations indicate readOnlyHint=true, and the description does not contradict. It adds behavioral context by describing the two-layer check (cookie expiry + probe URL redirect) and the return fields, which is helpful beyond annotations.

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 around 10 sentences with clear sections for return values and args. Each sentence adds value without excessive verbosity. Could be slightly more concise, but structure is good.

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?

Given the presence of an output schema (not shown but indicated), the description covers return fields and provides necessary context for using the tool. It adequately addresses the complexity of a session health check.

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 single optional parameter account_id is explained in the description: 'The account id to check. Omit to check the active account.' This adds meaning beyond the schema default of null and clarifies behavior.

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 clearly states the tool checks if the browser session is authenticated, with a specific verb and resource. However, it does not differentiate from the sibling tool 'gv_get_session_status', which may have similar functionality, preventing a higher score.

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 explicitly states the browser context must be open (calling gv_open_account first) for an accurate check, and mentions behavior when closed. It also explains when to omit account_id. No explicit when-not-to-use, but clear guidance is provided.

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