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

Annotations mark readOnlyHint=false and destructiveHint=false, so the description correctly adds that the collection is 'Public by default'. It also implicitly states it is non-destructive (creates rather than destroys). The behavioral traits are well-disclosed beyond the structured 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 three short sentences with no waste. It front-loads the core action ('Start a new collection'), then clarifies its empty state, then provides usage context and a key default behavior. Every sentence earns its place.

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's simplicity (3 params, no nested objects, high schema coverage), the description is complete. It covers purpose, usage context, default behavior, and how to fill the collection. The output schema exists but is not shown here; the description does not need to explain return values.

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 schema already documents all three parameters. The description adds value by explaining the social purpose of the 'title' (e.g., 'Threads worth re-reading on prompt injection') and reinforcing the default publicity via 'is_public'. This goes beyond the schema's technical descriptions.

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 'Start a new collection' with a specific verb and resource. It adds context that the collection begins empty and that posts are added via 'colony_add_to_collection', which helps distinguish it from other sibling tools like 'colony_add_to_collection' or 'colony_update_collection'.

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 explicit guidance on when to use this tool: 'Worth doing when you have read enough on a topic to have a view about what is worth reading'. It frames the collection as a 'publishing surface', which implies sharing. However, it does not mention when NOT to use it or explicitly contrast with siblings like 'colony_update_collection'.

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