monitor_storage_events

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

With no annotations, description covers key behavioral trait: cross-tab limitation. Also notes that events are recorded. However, does not mention potential side effects (e.g., event listeners added) or permissions needed.

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?

Two sentences with a crucial warning front-loaded. Every sentence provides value; no wasted words.

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 4 parameters, no output schema, and no annotations, description covers the core behavior and critical cross-tab limitation. Lacks specifics on output format for 'get' action but sufficient for agent to understand usage.

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%, so baseline 3. Description adds minimal extra meaning beyond schema: it mentions action and storageType but does not elaborate on tabId or apiKey behavior beyond schema descriptions.

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 it monitors localStorage and sessionStorage changes, with specific verb 'Monitor' and resource 'storage events'. It distinguishes from siblings like get_local_storage by emphasizing event-based cross-tab monitoring.

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 important usage guidance: storage events only fire in other tabs, not same-tab. Lists actions (start, stop, get) but does not explicitly compare to alternatives like polling get_local_storage for same-tab changes.

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