session_save

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

With no annotations, the description carries full burden. It discloses what is saved (cookies/localStorage) but does not address key behaviors: what happens if the name already exists (overwrite or error), whether an active browser session is required, or failure conditions. This is a mutation-like operation with significant gaps in side-effect disclosure.

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, efficient sentence that front-loads the action and purpose. Every word contributes meaning without redundancy.

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 one-parameter save operation with no output schema, the description covers the essential purpose and parameter adequately. It explains why the tool exists and what it stores. Minor gaps like overwrite behavior and session requirement prevent a 5, but the low complexity makes it reasonably complete.

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 100% with a basic 'Session name' description. The tool description adds only the phrase 'under a name', which clarifies the parameter's role but not constraints or uniqueness. Baseline 3 applies since the schema already documents the parameter.

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 specific verb (saves), a concrete resource (session state, explicitly cookies/localStorage), and the context (for tests with prior authentication). This distinguishes it from sibling tools session_list and session_delete, making the intent unmistakable.

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 gives a purpose context ('for tests with prior authentication') which implies when to use it, but it does not explicitly state when not to use it or compare against alternatives like session_list or session_delete. No exclusions or prerequisites are mentioned.

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