Read Web Storage

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. The description adds critical context: storage sensitivity (tokens, identifiers, personal data) and required acknowledgments. No contradiction.

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?

Three focused sentences, front-loaded with usage condition, no redundant text. Every sentence adds value.

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?

Use case and behavioral context are well covered, and output schema exists. However, with zero parameter description coverage and 5 parameters, the description is incomplete for effective tool invocation.

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%; the description does not mention any of the 5 parameters. Agents receive no guidance on origin, maxBytes, includeSessionStorage, or the acknowledgment booleans beyond schema field names.

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?

Description clearly states the tool reads localStorage or sessionStorage for authentication or application-state diagnosis, distinguishing it from sibling tools like browser_get_cookies or browser_get_state.

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?

Provides explicit preconditions (acknowledgeRawCapture, acknowledgeCredentialAccess) and next-step guidance (inspect relevant keys, avoid raw secrets). Implicitly restricts usage to contexts requiring full-profile auth or state diagnosis. Could be strengthened by directly stating when not to use.

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