get_collection_bookmarks

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Get all bookmarks' and does not mention response format, pagination behavior, permissions, or error conditions. This is a read operation but lacks necessary details for an agent to fully anticipate the tool's behavior.

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 a single, concise sentence with no redundant or filler content. It efficiently conveys the core action and scope.

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 the tool's simplicity (one parameter, no annotations, no output schema), the description is mostly complete for an agent to invoke it. However, the lack of any hint about the return structure or potential caveats (e.g., pagination) leaves a small gap, but it is adequate for a straightforward getter.

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 already describes collection_id as 'The collection ID' with 100% coverage. The tool description references 'a specific collection' but adds no extra meaning beyond the schema. The baseline of 3 applies because the schema fully documents the parameter.

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 'Get all bookmarks in a specific collection' uses a specific verb ('Get') and resource ('bookmarks') with a clear scope ('in a specific collection'). It clearly distinguishes from siblings like search_bookmarks (search) and get_highlights (highlights) by focusing on retrieving all bookmarks from a given collection.

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 when you need all bookmarks from a particular collection, but provides no explicit guidance on when to prefer this over search_bookmarks or when not to use it. There are no exclusions or alternative tool mentions, leaving the usage context implicit rather than stated.

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