Auto-Browser

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

No annotations are provided, so the description carries full burden. While 'Get' implies a read operation, the description doesn't confirm safety, idempotency, or whether the session must be active. It also doesn't describe what data the 'summary' contains or return format.

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?

Extremely terse at four words. While front-loaded and efficient, it borders on under-specification rather than valuable conciseness. No wasted words, but insufficient content for a tool with undocumented parameters.

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 zero schema coverage and no annotations, the description should explain both the input parameter and the output structure. It addresses neither, leaving critical gaps for an agent trying to invoke this tool correctly.

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 has 0% description coverage (session_id lacks a description field). The description fails to compensate by explaining the parameter, its format, or where to obtain valid session IDs (e.g., from create_session or list_sessions).

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 clear verb (Get) and resource (browser session summary) and implies singular scope ('one') which distinguishes it from list_sessions. However, it doesn't clarify what distinguishes a 'session summary' from other inspection tools like observe or get_html.

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?

Provides no guidance on when to use this versus list_sessions (which returns multiple sessions) or other session inspection tools. No mention of prerequisites like needing an active session or when this is preferred over fork_session.

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