browser_session

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

With no annotations, the description must disclose any side effects, permissions, or state changes. 'Session management' reveals nothing about whether the tool creates, destroys, or modifies sessions, nor what data it accesses. The agent has no basis to predict consequences of invoking it.

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 brief, but this is under-specification rather than conciseness. It has no wasted words because there are barely any words at all. A concise description would still convey essential information; this does not.

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?

For a tool with three parameters and no annotations or output schema, the description is entirely inadequate. It fails to explain what actions are valid, what scope and prefix mean, and what the tool returns. An agent cannot safely call this tool based on the provided information.

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?

Although schema coverage is 100%, the parameter descriptions ('Session scope', 'Session action', 'Session prefix') merely restate the names and add no meaning. The description adds nothing beyond the schema, and the schema itself is unhelpfully generic. An agent cannot infer valid values or relationships between parameters.

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 is 'Session management', which states a resource but no verb or specific operation. It fails to distinguish this tool from siblings like browser_state or browser_navigate, leaving the agent guessing whether it creates, deletes, or queries sessions. This is more informative than a pure tautology but still woefully vague.

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?

No guidance is provided on when to use this tool versus alternatives. There are no conditions, context hints, or mentions of sibling tools. The description gives zero information about the intended use case.

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