Import local storage

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that the operation occurs 'through the desktop app' and the data is from export_local_storage, but it does not disclose whether existing local storage is overwritten or merged. This is relevant behavioral context that is missing.

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, concise sentence with no wasted words. It front-loads the core action and immediately clarifies the data source. Appropriate length for the tool's simplicity.

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 description is adequate at a high level but lacks important operational details for a mutating tool with no output schema. It mentions the desktop app requirement but does not explain return behavior, prerequisites (e.g., profile must exist), or whether existing storage is replaced. These gaps make it only minimally 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 low at 33%—only localStorage has a description. The tool description adds context that the input is a dump from export_local_storage, but it does not clarify the purpose of the `plan` or `profileId` parameters. With such low schema coverage, the description should compensate by explaining these parameters, but it 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 clearly states the action: 'Write a local storage dump ... into a profile'. It uses a specific verb and resource, and references the counterpart tool `export_local_storage`, which distinguishes it from other import tools like import_cookies.

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 when to use the tool: to import a local storage dump produced by export_local_storage. However, it does not explicitly state when not to use it or name alternative tools beyond the producer reference.

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