zen_storage

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

With no annotations, the description must disclose behavioral traits. It lists allowed operations and parameter dependencies but omits side effects (e.g., permanent change on set/remove), permission requirements, or error scenarios. The per-origin mention adds useful context, but more detail on impacts would improve transparency.

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 concise, using bullet-like 'Args' format. It front-loads the purpose. While the docstring style is verbose, it efficiently conveys all necessary information without redundancy.

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 covers the basic operations and parameters. However, it lacks details on return values, error handling, and the permanence of modifications. For a storage tool, users need to know that set/remove/clear are irreversible, which is missing.

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 0%, so the description must explain parameters. It does: 'kind: local or session', 'op: get|set|...', 'key: Required for get/set/remove', 'value: For set, the string value. For restore, a dict.' This adds essential meaning beyond the bare schema types.

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 clearly states it handles 'localStorage / sessionStorage ops' and enumerates operations (get, set, remove, etc.). This is specific and distinct from sibling tools, which are mostly unrelated.

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 includes guidance: 'Storage is per-origin, so prefer driving it on a tab already at the right origin.' It also clarifies which parameters are required for which operations. However, it doesn't explicitly state when not to use this tool or compare to alternatives, though no similar sibling exists.

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