create_collection

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

Briefly describes basic behavior (create + optional parent). With no annotations, it minimally covers the action but omits details like whether it creates an empty collection or any side effects.

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 short sentences, no extraneous words. Efficiently conveys core functionality.

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?

For a simple creation tool with two parameters and no output schema, the description is largely complete. Minor gap: does not mention that collections can hold objects, but that is implied by 'folder for organizing objects'.

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?

Adds meaning beyond schema by explaining 'parent' as nesting. Schema has 0% description coverage, so description partially compensates, but does not specify format for 'parent' (e.g., ID or name).

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?

Clearly states the tool creates a collection (like a folder) and mentions nesting under parent. However, it does not differentiate from the similar sibling 'scene_create_collection', which could cause confusion.

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 on when to use this tool versus alternatives like 'list_collections' or 'move_to_collection'. Lacks any context on prerequisites or exclusions.

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