get_local_storage

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

No annotations provided, so description carries full burden. It states the operation is read-only and returns data, which is adequate but minimal. No additional behavioral details like performance implications or idempotency are given.

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?

Two short sentences that front-load the core functionality. Every word is necessary and no filler.

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?

As a simple read tool, it covers the essential aspects: what storage types, optional key filtering, and return content. No output schema, but the description adequately indicates the return shape. Minor omission: doesn't specify that it returns a dictionary of key-value pairs.

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 coverage is 100% with good descriptions for each parameter. The description adds marginal value by stating 'returns all entries or specific keys', which ties to the 'keys' parameter, but essentially repeats what the schema implies.

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?

Clear verb 'Read' and specific resource 'localStorage or sessionStorage from a session page'. Distinguishes from sibling set_local_storage as a read operation, and from other storage tools like get_cookies.

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?

Implicitly states when to use: to read storage values. No explicit when-not-to or alternatives mentioned, but the presence of sibling set_local_storage provides natural contrast. Strongly implied but lacks explicit exclusion.

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