get-bookmark-lists

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

The annotation readOnlyHint=true already communicates the read-only nature. The description adds the filtering criterion (contains a bookmark) but does not disclose other behavioral traits such as return format, pagination, or behavior for invalid bookmark IDs. It is consistent with the annotation, so no contradiction.

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, direct sentence that immediately states the tool's function with no unnecessary words or repetition. It is perfectly front-loaded and efficient.

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 simple read-only tool with one well-documented parameter and no output schema, the description adequately conveys the core behavior. It leaves minor gaps (e.g., whether the result is ordered, what happens for missing bookmarks) but these are not critical given the tool's simplicity and the supporting sibling context.

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 schema description for bookmarkId ('The id of the bookmark whose lists to retrieve') fully covers the parameter's meaning, achieving 100% coverage. The tool description adds no additional parameter semantics beyond restating the relationship, so the baseline of 3 applies.

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 'List every list that contains a bookmark' uses a specific verb (List) and resource (lists) with a clear scope (contains a bookmark). This distinguishes it from sibling tools like get-lists (all lists) and get-list-bookmarks (bookmarks within a list), making the purpose unambiguous.

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 provide guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. For example, it doesn't clarify that get-list-bookmarks would be used for the reverse direction, leaving usage context entirely implicit.

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