Create New Scene

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

The description discloses behaviors beyond annotations: it checks for unsaved changes, refuses by default, discards with force=True, and may ask for confirmation. The annotations already indicate destructiveHint=true, and the description adds context about the safety check and optional force behavior.

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 concise with three sentences, front-loaded with the primary purpose. Every sentence adds value: purpose, behavior, and confirmation note.

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?

Given the simplicity of the tool (one optional parameter), plus annotations and output schema, the description is complete. It covers the tool's core action, safety behavior, and additional context for form elicitation.

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 input schema covers 100% of parameters, with a description for 'force' already present. The tool description adds context by explaining the effect of force=True vs False, enhancing meaning beyond the schema.

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 'Create a new empty Maya scene,' providing a specific verb and resource. It distinguishes from sibling tools like scene.open, scene.save, etc., which have different actions.

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 explains that the tool checks for unsaved changes and refuses by default, and that using force=True discards changes. This guides the agent on when to use the force parameter. However, it does not explicitly mention when not to use this tool (e.g., if the user wants to keep unsaved changes), but the behavior is implied.

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