set_local_storage

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

With no annotations provided, the description carries full disclosure burden. It states 'Set a localStorage item' but does not explain persistence behavior, side effects (e.g., overwriting existing keys), permissions required, or return value. This is insufficient for safe invocation.

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 is appropriately front-loaded. However, it could include brief parameter context without losing conciseness.

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?

Given the tool's simplicity (set a key-value pair) and the existence of an output schema (not shown), the description is somewhat complete. However, it lacks context on browser scope, storage limits, or return value, which are relevant for an agent to verify success.

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%: the description adds no meaning beyond what the input schema already provides. The schema defines 'key' and 'value' as strings, but the description does not hint at their purpose, format, or constraints (e.g., valid key naming rules).

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 'Set a localStorage item' uses a specific verb and resource, clearly indicating the tool sets a key-value pair in localStorage. It distinguishes well from siblings like get_local_storage (reading) and clear_storage (removing all items).

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 no guidance on when to use this tool versus alternatives such as set_cookie or clear_storage. It does not mention prerequisites, context, or exclusions, leaving the agent to infer usage without direction.

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