create_collection

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

The only behavioral insight is that passing parent_id creates a sub-collection. Missing details include: whether it replaces existing collections, requires specific permissions, auto-generates any fields, or is idempotent. Without annotations, the description fails to adequately disclose behavioral traits.

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 concise at two sentences, but it omits critical information. It earns points for brevity but loses for under-specification – not every sentence is maximally informative.

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 complexity (4 parameters, 1 required) and no behavioral annotations, the description is incomplete. It fails to explain return values despite an output schema being present, and does not cover the full parameter semantics. A more complete description would at least list parameters and their effects.

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?

With 0% schema description coverage, the description adds no meaning to three out of four parameters (title, color, public). It only hints at parent_id. The agent must infer the role of title as required, and has no semantic insight into color or public.

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 action (create a new collection) and hints at the ability to create sub-collections via parent_id, distinguishing it from tools like update_collection or delete_collection. However, it lacks specificity about what constitutes a 'collection' in the domain.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., create_raindrop, update_collection). There is no mention of prerequisites, limitations, or scenarios where other tools would be more appropriate.

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