set_current_scene_collection

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

With no annotations, the description is responsible for behavioral disclosure. It adds the fact that the operation 'Blocks until the switch completes', which is useful. However, it does not mention error behavior, required permissions, or side effects beyond the switch itself, leaving some gaps.

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 two sentences long, front-loaded with the primary action, and contains no extraneous words. Every part earns its place, making it highly concise and well-structured.

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 setter with one parameter and no output schema or annotations, the description is mostly complete. It states the action and the blocking behavior, which is sufficient for an agent to invoke it correctly. It could mention that the name must exist, but the simplicity of the operation keeps the gap small.

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 coverage is 0%, so the description must compensate. The phrase 'by name' clarifies that the 'name' parameter is the identifier of the scene collection to switch to, which adds some meaning beyond the bare schema. Still, it provides no additional detail on constraints or source of the 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?

The description 'Switch to a scene collection by name' clearly identifies the action (switch) and resource (scene collection), with a specific scoping parameter ('by name'). This differentiates it from siblings like get_scene_collection_list (listing) and create_scene_collection (creation).

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 implies the tool is used to change the current scene collection, but does not explicitly state when to use it versus alternatives or mention prerequisites like obtaining a valid name from get_scene_collection_list. The usage is clear from context but not explicitly detailed.

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