manage_storage

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

With no annotations provided, the description carres the full burden and does so thoroughly: it explains get vs set behavior, the return values, storage origin scoping, and security implications around auth tokens and session identifiers. It also notes that storage is per-origin, which is crucial behavioral context.

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?

Information is well-organized under clear headings and the core purpose is front-loaded. There is some repetition about storage being origin-scoped and about not using run_javascript for arbitrary JavaScript, but it remains concise enough for an agent to parse.

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 covers purpose, selection, parameters, returns, and security, which is strong for a tool with no annotations and no output schema. A minor gap is that setting a null value is not explained, and the persistence distinction between local and session storage is only implied by their names.

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 0%, but the description fully compensates by explaining every argument: key, value, storage, and action. It even clarifies the conditional requirement that value is required when action='set', which the schema alone does not express.

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 opening sentence 'Get or set a key in localStorage or sessionStorage' names a specific verb, a concrete resource, and the storage type. It also distinguishes the tool from siblings by explicitly scoping it to Web Storage, not cookies, content, or JavaScript execution.

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 provides an explicit tool-selection section listing when to use this tool versus manage_cookies, run_javascript, get_content, and get_attributes. It also gives clear 'When not to use' exclusions, making the selection decision unambiguous.

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