save_browser_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 explaining side effects. It only indicates 'save,' leaving unclear whether this overwrites an existing session, where the session is stored, whether it is persistent, or what happens on failure.

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 text is extremely short, but this is under-specification rather than conciseness. Every word aligns with the name, yet it omits essential behavioral and uusge information needed for effective tool invocation.

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 persistence action with no annotations and no output schema, the description must clarify what state is changed, how the session is identified, and what the caller should expect. None of that information is present, so the tool cannot be invoked confidently.

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 input schema shows a single string parameter 'sessionName' with no description, and the tool description does not clarify expected format, naming rules, or semantics. The parameter name is somewhat self-explanatory, but with 0% schema description coverage, the description should compensate and does not.

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 a direct restatement of the tool name: 'Save browser session' adds no detail beyond the name itself. It is not misleading, but it does not explain what a browser session is or what saving entails, and it does not differentiate from siblings.

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, what prerequisites exist, or whether an active browser session must be present. The description only states the action without any context for selection.

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