Set Web Storage

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description confirms this by stating 'this changes potentially credential-bearing application state' and requiring acknowledge flags. No contradiction, and it adds context about credential sensitivity beyond annotations.

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 four sentences, somewhat concise, but the first sentence is long and could be broken for readability. It avoids waste but lacks structured presentation of preconditions and steps.

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?

With destructive behavior and output schema present (not shown), the description covers preconditions and sensitivity but fails to detail parameter usage. It is complete for high-level context but lacks parameter guidance given 0% schema coverage.

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 coverage is 0%, so description must compensate. It only mentions acknowledgeRawCapture and acknowledgeCredentialAccess as prerequisites, but does not explain origin, localStorage, or sessionStorage parameter semantics. This is insufficient for correct usage.

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 title 'Set Web Storage' and description explicitly state the tool sets localStorage/sessionStorage values. It clearly distinguishes from siblings like browser_set_cookies and browser_get_storage by specifying controlled web storage manipulation.

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 specifies when to use: 'full-profile authorized test explicitly needs controlled localStorage or sessionStorage values'. It provides preconditions (acknowledge flags) and next steps (reload/navigate). While it doesn't explicitly exclude other scenarios, the context is clear.

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