indexeddb_list

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

With no annotations present, the description carries the full burden. It discloses that the operation is scoped to the current origin and highlights that IndexedDB content is invisible to cookie/localStorage tools, which is useful behavioral context. The word "List" clearly implies a read-only operation, though it does not detail the exact return shape.

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, first one front-loaded with the core action and scope, second one adding motivation and differentiation. Every sentence earns its place and there is no fluff.

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 zero-parameter list operation, the description is largely complete: it names the resource, scope, and why an agent would need it. The only minor gap is that it does not explicitly describe the return format, but for a simple 'list databases' tool this is reasonably inferable.

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 tool has zero parameters and the schema already covers 100% of the parameter surface. Description adds no parameter details, but none are needed. This matches the baseline of 4 for a no-parameter tool.

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 and resource: "List IndexedDB databases for the current origin." It clearly distinguishes this tool from the many cookie and localStorage siblings by noting that SPA auth state and drafts live in IndexedDB and are invisible to those other tools. An agent can tell exactly what this tool does.

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 gives clear context for when to use this tool: when investigating SPA state that is stored in IndexedDB and not visible to cookie/localStorage tools. It does not name specific alternative tools or state explicit when-not conditions, but the guidance is enough to route an agent correctly.

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