Create Collection

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

The description reveals that the tool 'writes workspace sidebar metadata,' providing behavioral context beyond the annotations (e.g., that it is a lightweight metadata write rather than a document operation). This aligns with readOnlyHint=false and idempotentHint=false without contradicting any 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?

The description is two sentences long, front-loaded with the primary action, and immediately adds a clarifying constraint. Every word earns its place with no redundant or vague language.

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 a rich schema (3 params, nested rules object) and output schema present, the description need not explain return values. It provides essential context about the tool's side effect (writing sidebar metadata) and its boundary (not creating documents), making it sufficient for a create operation.

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 already provides 100% coverage with descriptions for all parameters (name, rules, workspaceId). The description only mentions 'optional rules,' which adds no new semantic detail beyond what the schema already provides. Baseline of 3 is appropriate.

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 'Create a new AFFiNE sidebar collection with optional rules' with a specific verb and resource. It also explicitly distinguishes what it does not do ('does not create documents'), setting it apart from document creation tools and clarifying its scope.

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 communicates when to use the tool (creating a new collection) and provides an exclusion by noting it does not create documents. However, it does not explicitly mention alternatives like update_collection or list_collections for other collection operations, so usage guidance is clear but not fully comprehensive.

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