export_session

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

With no annotations, the description carries full burden. It states what data is exported and the output format, but does not clarify whether the operation is read-only, how the optional tabId affects scope (specific tab vs all), or any limitations. The verb "export" implies non-destructive, but this is not explicit, and the tabId ambiguity creates a transparency gap.

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 conveys the essential information without fluff. Every phrase earns its place: it names the verb, resource, included components, and output format, making it highly concise and well-structured.

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 one optional parameter and no output schema, the description covers the core purpose and output format but omits clarification on how tabId affects the export scope. Without this, the agent may not understand whether omitting tabId exports all sessions or only the current one. The description is adequate but has a clear gap.

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 already documents the single optional parameter (tabId) with 100% coverage. The description does not add any additional meaning about how tabId influences the exported session state, so it relies entirely on the schema. This meets the baseline for high schema coverage but adds no extra value.

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 uses a specific verb ("Export") and resource ("complete session state") and explicitly lists the contained data types (cookies, localStorage, sessionStorage) and output format (JSON). This clearly distinguishes it from sibling tools like set_cookie or import_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 phrase "for later import" explicitly indicates the primary use case (saving state to restore later), which implies pairing with the import_session sibling. It does not state when not to use it or name alternatives, but the context is clear enough for an agent to select it appropriately.

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