create_collection

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the action without mentioning side effects, failure conditions, permissions, or whether the collection name must be unique. This is insufficient for a mutation tool.

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, focused sentence that efficiently communicates the core action, with no unnecessary words. It is front-loaded and easy to parse, though its brevity contributes to the lack of context that penalizes other dimensions.

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?

The tool has one required parameter and no annotations, so the description should provide sufficient context for correct invocation. It fails to mention prerequisites like an active scene, error conditions, or how this differs from similar collection tools. The presence of an output schema reduces the need for return-value explanation, but the overall usability guidance is still lacking.

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 0%, so the description must compensate by explaining the 'name' parameter. It does not: it adds no information beyond the schema's title 'Name', leaving naming conventions, restrictions, or meaning undefined.

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 'Create' and the resource 'a new collection', and adds the linkage to the active scene, which conveys the core action. However, it does not explicitly differentiate from sibling tools like create_collection_hierarchy or instance_collection, so it stops short of a full 5.

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 about when to use this tool versus alternatives such as create_collection_hierarchy, instance_collection, or move_to_collection. The description gives no context on prerequisites, scenarios, or exclusions, leaving the agent to infer usage.

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