List bookmarks

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

With no annotations provided, the description carries the behavioral transparency burden. 'List' is a clear read operation and the phrase 'local JSON store' specifies the data source and implies no network or destructive side effects. It still doesn't explicitly state that bookmarks are never modified, but the wording is strong enough for a simple list tool.

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, information-dense sentence that front-loads the main action and scope. Every word contributes meaningful context, leaving no excessive or irrelevant prose.

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, read-only listing tool, this description is largely sufficient. It lacks explicit mention of empty-store behavior or the exact return shape, but the description's scope and the tool's naming make it reasonably complete for an AI agent.

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 input schema has zero parameters and 100% schema description coverage, so the description does not need to explain parameter details. The phrase 'List all saved bookmarks' clarifies the point of the result without adding unnecessary parameter-level noise.

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 (List) and resource (all saved bookmarks) and identifies the data source (local JSON store). This matches the title while also giving enough semantic scope to distinguish it from add_bookmark and search_bookmarks.

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 does not state when to use this tool versus its siblings. It implies enumeration of the full set of bookmarks, but it never mentions that search_bookmarks should be used for filtered or specific lookups, or that add_bookmark is for creation.

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