Get Session

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only says 'Get metadata' without specifying what metadata is returned, whether the session must be active, error behavior for invalid sessionIds, or whether the operation is read-only. This is minimal disclosure for an operation with no output schema.

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, front-loaded sentence that directly states the tool's purpose with no filler. It is appropriately concise for a simple get operation.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'metadata' means (e.g., fields like browser version, session status), the return format, or error handling for invalid session IDs. For a tool with one parameter and no output schema, more context is needed to ensure correct invocation.

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?

Schema description coverage is 0%, so the description must compensate for the parameter semantics. However, it merely restates 'by sessionId' without adding meaning about the expected format, how to obtain a sessionId, or any constraints beyond what the schema already shows (type: string, required). The description adds no value beyond the schema.

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 action (Get metadata) and the resource (browser session) with a specific parameter (sessionId). It distinguishes from sibling tools like list_sessions (which lists all sessions) and create_session/close_session by focusing on retrieving metadata for a single session.

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 implies usage when you have a sessionId and need metadata, but it does not explicitly state when to use this tool versus alternatives like list_sessions or how to obtain a sessionId. There is no exclusion guidance or alternative tool reference.

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