Export local storage

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

Annotations already mark the tool as read-only, so the description's mention of 'Keys and values are Base64-encoded and are normally treated as an opaque blob' adds valuable behavioral detail beyond that flag. It tells the agent not to parse the contents and that the data is grouped by origin. However, it omits any auth or rate-limit context, which keeps it below a 5.

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 two short sentences that lead with the core purpose and add a key behavioral detail. Every word earns its place; there is no repetition of schema or annotation information.

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?

The tool has no output schema, and the description does not specify the return format or how the export is delivered (e.g., file vs JSON). It also omits prerequisites like the desktop app needing to be running or the plan parameter's role. The description covers basic behavior but is not fully complete for an agent choosing to invoke it.

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 only 25% (only browserProfilePassword has a description), and the tool description does not explain any parameters. With low coverage, the description should compensate, but it does not mention browserProfileId, plan, or cloudSyncDisabled, leaving their semantics to be guessed from names alone.

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+resource: 'Export a profile's local storage through the desktop app, grouped by origin.' This clearly distinguishes the tool from siblings like import_local_storage and export_cookies by specifying the operation, resource, and scoping (by origin).

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 the tool is for exporting local storage in a migration/backup context, but it does not explicitly state when to use it instead of alternatives like import_local_storage or export_cookies. There are no exclusions or alternative mentions, so usage guidance is minimal and only inferred.

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