unity_scene_new

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

No annotations provided, so description carries full burden. It doesn't mention potential side effects (e.g., unsaved changes, scene lifecycle) or return value. Adequate for a simple creation tool but lacks behavioral detail.

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?

Single, clear sentence with no wasted words. Front-loaded with purpose. Appropriate length for the tool's simplicity.

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 no output schema and simple single parameter, description is mostly complete. However, missing context about what happens to current scene, success/failure feedback, or whether it replaces existing scene. Adequate but could include more.

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 100% with one parameter (port). Description adds value by explaining port's purpose and referencing unity_select_instance, which helps agents understand routing context. No additional meaning needed beyond 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?

Description clearly states 'Create a new empty scene', using specific verb 'Create' and resource 'scene'. It distinguishes from siblings like unity_scene_open and unity_scene_save, though lacks explicit differentiation from other creation tools.

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?

No guidance on when to use this tool versus alternatives (e.g., unity_scene_open, unity_gameobject_create). The description implies creating a new scene but doesn't specify prerequisites, typical workflow, or exclusions.

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