load_scene

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the action without revealing side effects (e.g., whether the current scene is replaced), file format requirements, or error behavior. The agent has no information beyond the basic action.

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 one action sentence plus an explicit Args block for the parameter. It is tightly written, front-loaded with the purpose, and contains no filler.

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 is straightforward with a single parameter and has an output schema, so the description covers the basic invocation. However, it lacks useful context like file format expectations or whether loading overwrites the current scene. It meets the minimum viable threshold but does not go beyond it.

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 itself gives 'File Path' as a plain string with no description, so the description adds meaningful semantics: 'Path to the scene file to load.' This tells the agent what the parameter means and how it is used, though it omits details like supported extensions or relative/absolute path conventions.

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 ('load') and a specific resource ('Cinema 4D scene file'), which clearly distinguishes it from sibling tools like save_scene and get_scene_info. The action is immediately understandable.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention that loading a scene is a prerequisite for other operations, nor does it state any exclusions or alternatives.

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