Scene New

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

With no annotations provided, the description carries the full disclosure burden, yet it says nothing about what happens to the current scene or its unsaved changes. The fact that creating a new scene can destroy in-progress work is only hinted at indirectly by the schema's 'force' parameter, not by the description. That is a material omission for a state-replacing operation.

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?

A single front-loaded sentence with zero filler. It states the action and result immediately with no redundancy.

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?

An output schema exists, so return values need not be explained. However, for a tool that replaces the current scene, the description omits the behavioral context an agent needs: whether unsaved work is discarded or prompted, and whether a session must be active. The description is too thin for the destructive potential of this operation.

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 100%, so both 'force' and 'session_key' are already documented in the schema and the baseline is 3. The description adds no parameter meaning beyond that, contributing nothing extra.

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?

States a specific verb and resource ('Create a new, empty scene'), which cleanly separates it from siblings like scene_open and scene_save. It doesn't explicitly name a sibling or state the distinguishing condition, but the operation is unambiguous.

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?

There is no guidance on when to use this rather than scene_open, or on prerequisites such as needing an active Maya session. Usage is only inferable from the verb 'Create', with no conditions or exclusions stated.

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