browser_set_local_storage

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

No annotations are provided, and the description only says 'Set LocalStorage' without disclosing whether it overwrites existing values, whether it requires a page context, or any other behavioral traits. It implies a write operation but adds no detail beyond what is already obvious from the name.

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 extremely short, which is concise, but it under-specifies the tool's behavior and parameters. It does not earn its place as a helpful description; it's more of a label than a functional description, so the brevity is not a positive trait here.

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, the description still omits essential context: no return value, no prerequisites, no side effects, and no cross-references to related storage operations. With no annotations and no output schema, the description is the only source of context, and it is insufficient.

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 schema has two parameters (key, value) with 0% description coverage. The description does not explain the meaning, format, or constraints of these parameters, so it fails to compensate for the schema's lack of descriptions. The parameter names are somewhat self-explanatory, but the description adds no explicit semantics.

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 '设置' (set) with the resource 'LocalStorage', clearly indicating an action to set a local storage value. It differentiates from sibling tools like browser_get_local_storage and browser_clear_local_storage by the action performed. However, it does not explicitly mention the key-value pair structure, though the schema provides that.

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 offers no guidance on when to use this tool versus alternatives, no prerequisites (like needing a page loaded), and no exclusions. It simply states the action without any context, leaving the agent to infer usage.

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