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

Annotations already mark this as read-only and idempotent; the description adds meaningful behavior beyond that: reverse capture ordering, nextCursor presence when more pages exist, and a crucial constraint that a cursor only works with identical filters, collection, and state. No contradiction with annotations.

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?

Three sentences, all high-signal: primary behavior, alternative tool, and the pagination caveat. No fluff or repetition of schema defaults.

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 read-only browsing tool with an output schema and rich annotations, the description covers what the agent needs: what it lists, how ordering works, how pagination and cursor validity behave, and when to prefer a sibling. The remaining parameter details are appropriately left to the schema.

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 description gives useful semantic guidance for cursor (exact-match requirement) and collectionId (browse saved collection contents), but leaves the many nested filter parameters as generic 'structured filters.' With schema description coverage at 40%, the description partially compensates but does not fully carry the load for limit/state/filter semantics.

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 states a specific action ('Browse bookmarks') with a clear resource and two modes: structured filters and saved collection via collectionId. It also says ordering is reverse capture order and explicitly names 'search' as the sibling for free-text discovery, so an agent can distinguish it from search without opening schemas.

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?

It tells the agent exactly when to prefer a different tool: 'Prefer search for free-text or semantic discovery.' It also clarifies the collection alternative with collectionId as a distinct browsing path, which is explicit routing guidance relative to the sibling list_collections/search tools.

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