get_storage_data

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Dump' clearly implies a read-only operation, which is correct, but it does not explain what the output format is, whether both storage areas are returned together or separately, or any edge cases (e.g., empty storage). This is adequate for a low-risk read operation but lacks detail.

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 a single sentence with no filler. It is direct and front-loaded, stating exactly what the tool does. Every word contributes to the purpose, and there is no unnecessary elaboration.

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 tool has no output schema, so the description must convey return value structure. It only says 'dump contents,' which is vague about the format (e.g., JSON string, object with separate keys, raw text). Without this information, the agent cannot reliably parse the result. Given the simplicity of the task, this is a significant gap.

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?

The tool has zero parameters, and the schema is empty. The description is the only source of meaning, and it clearly names the two storage types being accessed. Since there are no parameters to explain, the baseline for zero-parameter tools is 4, and the description suffices.

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 'Dump localStorage and sessionStorage contents.' uses a specific verb ('dump') and a clear resource (localStorage and sessionStorage). It unambiguously distinguishes this from sibling tools like get_cookies or set_storage_item, which deal with other storage domains.

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 provides no guidance on when to use this tool versus alternatives. It does not mention typical scenarios (e.g., inspecting storage before/after actions) or exclude cases where another tool might be better (e.g., get_cookies for cookies). The lack of explicit usage context leaves the agent to infer solely from the tool name.

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