interceptor_browser_list_storage_keys

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

No annotations provided. The description mentions pagination and truncated value previews, but lacks details on side effects, permissions, or error states. It does not contradict 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?

A single, concise sentence (12 words) conveying all essential information with no redundancy.

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 is adequate for a 7-parameter tool with no output schema, but lacks details on return format, behavior when no keys match, or how pagination is indicated. More context would improve completeness.

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 100% with detailed parameter descriptions. The tool description adds minimal value beyond 'pagination and truncated value previews', which is already implied by parameters like offset, limit, and value_max_chars.

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 clearly states it lists localStorage/sessionStorage keys for the current origin, with pagination and truncated value previews. It implicitly distinguishes from sibling 'interceptor_browser_get_storage_value' which gets a specific value.

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 gives no explicit guidance on when to use vs alternatives like 'interceptor_browser_get_storage_value' or when not to use. Usage is implied but not stated.

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