storage_get

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'Read' which implies non-destructive behavior, but does not disclose return format, behavior when keys are omitted, or the significance of the direct parameter (like bypassing a crashed Service Worker) beyond what the schema already provides.

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 one short sentence, very efficient with no wasted words. However, it is arguably under-specified for a tool with three parameters and no output schema, so it loses a point for not using the space to add helpful context.

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?

Given no output schema and no annotations, the description is incomplete. It does not explain what the tool returns, how keys are handled when omitted, or the practical context for the direct flag. The description is too brief to fully equip an agent to use the tool correctly in all scenarios.

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%, so the baseline is 3. The description repeats the area enum (local/sync/session) already in the schema and adds no additional meaning about keys or direct parameters. Thus it provides no extra value beyond the structured 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 says 'Read from chrome.storage (local/sync/session)' which clearly identifies the verb (read) and resource (chrome.storage), and differentiates from sibling storage_set (write). It is specific about the storage areas, though it doesn't mention key retrieval semantics.

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 implies usage: read storage when you need to retrieve values. However, it does not explicitly state when to use this tool vs storage_set or other alternatives, nor does it mention exclusions like preferring direct mode in certain scenarios.

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