get_local_storage

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states the read-only nature via 'Get' and explicitly discloses the fallback behavior (return all keys when no key is given). It does not mention edge cases like missing keys or value formatting, but the core behavior is transparent.

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 sentence with no unnecessary words. The primary action is front-loaded, followed by the optional-key fallback. Compact yet complete for a tool this simple.

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?

For a simple optional-parameter getter with no output schema, the description covers the main use cases well. The only minor gap is that the return format for 'all keys' (e.g., array vs. object) is not specified, but this is unlikely to block correct invocation.

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 provides 100% coverage with 'localStorage key (omit for all)', and the description's 'if no key is given' only restates that. No meaningful semantic is added beyond the schema, so the baseline of 3 applies.

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 verb ('Get'), resource ('localStorage'), and the no-key fallback behavior in one short sentence. This makes it easy to distinguish from siblings like get_session_storage and set_local_storage without opening schemas.

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?

Describes the two calling modes (with and without a key), which implicitly guides usage, but does not explicitly state when to prefer this tool over alternatives like get_session_storage or set_local_storage. The intended context is implied by the resource name rather than stated as guidance.

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