unity_editor_state

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

No annotations provided, so description must carry burden. It describes a read operation (Get) but doesn't specify if it's destructive or has side effects. Given no destructive hint, a read assumption is reasonable, but the description could be more explicit about non-mutating 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?

One-sentence description is extremely concise and front-loaded. Every word adds value, covering four key aspects of the state. No unnecessary information.

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, description should hint at return value. It lists four state elements (play mode, compilation, active scene, project path) but doesn't specify structure. For a simple read tool with good annotations, it's adequate but could be more complete.

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 a well-described port parameter. Description adds no additional parameter info beyond the schema. Baseline 3 is appropriate since schema does the heavy lifting.

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 it retrieves Unity Editor state including play mode, compilation, active scene, and project path. This distinguishes it from siblings like unity_project_info (project-level) and unity_play_mode (play mode control), but could be more explicit about what specific state fields are returned.

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 explicit when-to-use or when-not-to-use guidance. The description implies it's for reading current editor state, but doesn't contrast with tools like unity_project_info or unity_scene_info. The port parameter description provides some guidance for parallel instances.

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