get-tag-bookmarks

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

No annotations are provided, so the description carries the full burden. It only states basic behavior (list, pagination) without disclosing read-only nature, error handling of invalid tagId, rate limits, or default behaviors like sort order or content inclusion.

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?

A single sentence with no wasted words. It is front-loaded with the action and resource, and includes key qualifier 'with pagination'. Highly efficient for its length.

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?

With 5 parameters and no output schema or annotations, the description is minimal. It covers pagination but lacks details on parameters like cursor usage, sort order defaults, or behaviors of includeContent. Schema fills some gaps, but overall incomplete for a complex 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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema definitions, only mentioning 'pagination' generically. No value added over structured data.

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 tool lists bookmarks filtered by a specific tag, with pagination. It uses specific verb 'list' and resource 'bookmarks', distinguishing it from sibling tools like 'get-bookmark' (single) or 'search-bookmarks' (broad).

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 pagination for large result sets but does not explicitly state when to use this tool versus alternatives like 'search-bookmarks'. No when-not-to-use guidance or prerequisites provided.

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