get_storage

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

The description indicates a read operation (non-destructive) and limits output to 'names' rather than values. However, with no annotations, it could provide more detail about permission requirements, performance, or edge cases (e.g., empty storage).

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, well-formed sentence that conveys the tool's purpose without redundancy. Front-loaded with the verb and resource, 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 the tool's simplicity (zero parameters, no output schema), the description adequately covers its functionality. It could mention the condition that a page must be loaded, but the overall context is sufficient for an agent.

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?

There are no parameters, so the input schema is fully covered. However, the description does not add behavioral context beyond the schema. Baseline 3 is appropriate given 100% schema coverage.

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 explicitly states the tool reads cookies, localStorage, sessionStorage, and IndexedDB names for the active page. It uses a clear verb ('Read') and specific resources, distinguishing it from sibling tools that deal with DOM, console, network, etc.

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?

No guidance is provided on when to use this tool or when to choose alternatives. It does not mention exclusions, prerequisites, or comparisons to other storage-related tools.

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