List Collections

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only restates the purpose without adding details about scope (e.g., pagination, sorting, authentication requirements), or any side effects (e.g., no mutations). The description is insufficient for an agent to anticipate behavior beyond the obvious.

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 concise sentence that directly states the action and target. It avoids unnecessary words but is not structured with headings or bullets. It is appropriately sized for a simple tool.

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 tool has one parameter, no output schema, and limited sibling context, the description is too minimal. It does not specify the return structure (e.g., list of collection IDs, names), whether the list is ordered, or if there are any limits. An agent would lack key details to interpret results correctly.

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 input schema has a parameter workspaceId with no description; schema description coverage is 0%. The description does not clarify the purpose or constraints of workspaceId (e.g., required? default? format). It adds no semantic value beyond the schema itself.

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 verb 'List' and the resource 'AFFiNE collections stored in the workspace sidebar.' It distinguishes from siblings like get_collection, create_collection, delete_collection, and update_collection by indicating it returns a list rather than a single item or performing mutations.

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 provides no guidance on when to use this tool versus alternatives (e.g., get_collection for a specific collection, search_docs for search over collections). There is no mention of context, prerequisites, or exclusion criteria.

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