storage_get

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds meaningful context: omission of key triggers a full dump, values are truncated past ~20k chars, and truncation is reported. It doesn't cover offset or max_items pagination, but core behavior is clear.

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 sentences with no filler; the primary usage decision is front-loaded. Every sentence contributes either to operation, parameter behavior, or defaults.

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?

Covers the main read/dump path and truncation reporting well, but an agent is left guessing about offset, max_items, and timeout behavior when dealing with large storage or pagination. The output schema mitigates return-value ambiguity, but parameter behavior is incomplete for a tool with this many knobs.

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 description coverage is 0%, so the description must compensate. It adds real meaning for key, area, and indirectly max_bytes via the truncation threshold, but leaves offset, timeout, max_items, and session_id without explanation. This is a partial but not complete compensation for a 7-parameter tool.

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?

States a specific read operation against localStorage or sessionStorage, and clearly differentiates from its write sibling storage_set. The per-key vs dump-all behavior is explicit, leaving no ambiguity about what the tool does.

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 concrete usage instructions: give a key for one value or omit it to dump all keys, and choose local or session area. It doesn't explicitly contrast with storage_set, but the read/write distinction is obvious from the verb and sibling name.

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