create_scene_collection

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

With no annotations, the description carries the full burden. It explicitly states the two-step behavior (create and switch), but does not disclose error conditions like duplicate names, potential side effects on existing collections, or any required permissions. The core behavior is clear, but additional context is sparse.

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 sentence that conveys both the primary action and the switching side effect without any fluff. Every word earns its place, making it highly concise and front-loaded.

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 tool with one parameter and no output schema, the description provides the essential behavior, including the switching side effect. It is sufficient for an agent to know when and how to invoke it. Some minor details about error handling are absent, but they are not critical for this simplicity.

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 schema has 0% description coverage, so the description must compensate. It implies that 'name' refers to the name of the new scene collection, but it adds no constraints or format details. With only one self-explanatory parameter, a 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 uses a specific verb 'create' with a clear resource 'scene collection', and additionally states the side effect 'and switch to it'. This makes it distinct from sibling tools like set_current_scene_collection, which only switches to an existing 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 conveys a clear use case: when a new scene collection is needed and should become active. It doesn't explicitly mention alternatives, but the combined create-and-switch action inherently distinguishes it from tools that list or switch collections, providing clear context without exclusions.

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