localstorage_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the operation without explaining that it is read-only, what the return format is, whether a page must be loaded, or how missing keys are handled. The description is not misleading but lacks meaningful behavioral context.

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, front-loaded sentence with no filler words. It conveys the essential split between retrieving all data and retrieving one key efficiently.

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 should compensate by explaining what the response looks like. It does not say whether the result is a JSON object, a value, null, or an error for a missing key. An agent is left guessing about the return shape, which is a significant gap for a retrieval tool.

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 schema already documents the single 'key' parameter with 'empty = all', and the tool description reinforces this with 'all localStorage data or a specific key.' With 100% schema description coverage, the baseline is 3; the description adds no new semantic detail beyond the schema.

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 uses a specific verb ('Get') and resource ('localStorage data'), and clarifies the two modes: all data or a specific key. It is distinguishable from localStorage_set/localstorage_clear, but it does not explicitly differentiate from sessionstorage_get or storage_snapshot.

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 phrase 'Get all localStorage data or a specific key' implies the tool is for reading localStorage entries, which is decent context. However, it gives no explicit guidance on when to use this tool versus sibling storage tools, nor any exclusions or preconditions.

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