storage_set

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions 'Write' but does not explain whether it overwrites existing keys, merges data, requires special permissions, or what the return value/error behavior is. This leaves significant behavioral ambiguity.

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: 'Write to chrome.storage (local/sync/session).' Every word earns its place, and there is no filler or 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?

This is a simple two-parameter tool with complete schema coverage, so the description need not explain parameters. It covers the core purpose and storage areas, which is largely sufficient. However, it omits behavioral details such as whether writes merge or overwrite existing data, which could matter in some contexts.

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 provides descriptions for both parameters (area and data) with 100% coverage, so the baseline is 3. The description adds no parameter-level detail beyond restating the enum values (local/sync/session), meaning it does not elevate above the schema.

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 the specific verb 'Write' and names the resource 'chrome.storage' with the scoping areas (local/sync/session). This clearly identifies the tool's function and distinguishes it from the sibling storage_get.

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 verb 'Write' implies this tool is for storing data, providing some contextual guidance. However, there is no explicit statement of when to use this tool over storage_get or other alternatives, nor any exclusions.

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