list_collections

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly implies a read-only listing operation and defines the scope ('all your bookmark collections'), which is transparent for a simple list tool. However, it does not describe return format, pagination, or other behavioral details, though these are less critical for a parameterless list operation.

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, succinct sentence that fully conveys the purpose, enhanced by a helpful analogy. There is no redundancy, filler, or unnecessary detail.

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 simplicity of the tool (0 parameters, no output schema, no annotations), the description is mostly complete. It explains what the tool does and its scope. It could optionally mention what a collection contains or point to related tools, but these are already implied by sibling names the agent receives. The lack of output schema slightly increases the burden, but the description's clarity compensates.

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 tool has zero parameters, and the schema covers 100% of them (vacuously). Per the rubric, 0 params gives a baseline of 4. The description does not need to explain parameters, and it appropriately focuses on the tool's purpose.

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 uses a specific verb 'List' with a clear resource 'bookmark collections' and provides an analogy ('like playlists for tweets') that makes the concept immediately understandable. It distinguishes from siblings like get_collection_bookmarks (which lists bookmarks within a collection) by clarifying this lists the collections themselves.

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 for retrieving all bookmark collections but does not explicitly state when to use this tool versus alternatives. There is no mention of when not to use it or pointers to siblings such as get_collection_bookmarks or create_collection, so the guidance is only implicit.

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