Open Scene

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

Despite annotations indicating destructive hint, the description adds context by detailing the check for unsaved changes and the force parameter behavior, though it doesn't explicitly state that the current scene is replaced.

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 (4 sentences), front-loaded with the main action, and each sentence provides necessary detail without 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?

The description sufficiently covers the tool's behavior given the output schema exists, though it could mention that the current scene is replaced or provide error handling details.

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?

With 100% schema coverage, the description still adds value by clarifying the force parameter's effect ('Use force=True to discard unsaved changes') and confirming that file_path is validated and formats supported.

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 it 'Open a Maya scene file' and mentions validation, unsaved changes check, and supported formats, distinguishing it from sibling tools like scene.new, scene.save, etc.

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 when to use force=True to discard unsaved changes and mentions form elicitation for confirmation, but lacks explicit guidance on alternatives like scene.import for external files.

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