List bookmarks

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

With no annotations, the description bears the full burden of behavioral disclosure. It mentions 'detected browsers' and pagination, offering some context, but it does not clarify default behavior (e.g., returns all bookmarks if no filter), the meaning of source filtering, or any prerequisites like running list_sources first.

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 and well-structured: two short sentences, front-loaded with the main action, and no unnecessary words. It efficiently communicates the core functionality.

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?

The description covers the basic listing function but omits significant details such as the source filter option, how 'detected browsers' relates to list_sources, and default pagination behavior. Given no annotations and no output schema, it is moderately complete but leaves important gaps for effective tool selection and invocation.

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 only 50% (folder and source described). The description adds 'folder filter' and 'pagination,' giving partial meaning to limit/offset, but it does not explain their specific semantics or mention the source parameter. This provides some compensation but not enough for full clarity.

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 the action ('List bookmarks') and the resource ('detected browsers'). It conveys the primary function effectively, though it does not explicitly distinguish it from sibling tools like search_bookmarks or recent_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?

No guidance is provided on when to use this tool versus alternatives. The description only mentions capabilities (folder filter, pagination) without indicating when one would choose this over search_bookmarks or other siblings.

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