List Collections

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful prerequisite context before mutations and says it returns collection rules, but it does not add further behavioral detail such as pagination, permissions, or result scope beyond the 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?

Two sentences with no wasted text, and the core purpose is front-loaded before the usage guidance. The phrase 'read-only' repeats the annotation slightly, but it does not harm efficiency.

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 an output schema, rich annotations, and a fully documented single parameter, the description gives enough context to call the tool correctly. It could be slightly stronger by clarifying how it relates to get_collection, but nothing essential is missing.

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 single workspaceId parameter is fully documented in the schema. The description adds no parameter-specific guidance, which is acceptable at baseline 3 when the schema already does the work.

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 and resource: 'List AFFiNE sidebar collections and their rules.' It is clear what the tool returns, but it does not explicitly distinguish itself from the sibling get_collection beyond the plural 'List.'

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 gives a clear usage context: 'Use this read-only tool before updating, deleting, or adding documents to a collection.' This tells the agent when to call it, though it does not name the specific alternative mutation tools or state when not to use it.

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