List Bookmarks

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

The description discloses that results are sorted newest first and lists the returned fields (title, summary, source feed, link). With no annotations, these details help agents understand the tool's behavior. However, it does not mention pagination behavior beyond the schema parameters.

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, no fluff. The key behavior and return fields are front-loaded. Every word adds value.

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 no output schema, the description adequately specifies return fields. It covers sorting and resource type. Could optionally mention user scope (e.g., 'your bookmarks'), but not essential for a simple list tool.

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 100%, so the parameter descriptions are already provided. The description adds value by confirming the ordering context for pagination ('newest first'), which helps agents understand how offset works. No additional detail needed.

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 identifies the action ('list'), the resource ('saved feed item bookmarks'), and the ordering ('newest first'). It distinguishes from sibling tools like bookmark_item (create) and remove_bookmark (delete).

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 the tool is used to view bookmarks but does not explicitly state when to use it over alternatives or when not to use it. No exclusions or context about prerequisites are provided.

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