editor_control

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

Annotations only indicate readOnlyHint: false (mutation allowed). The description lists actions like open/close and lock, implying mutations, but lacks details on side effects, permissions, error handling, or return values. For a tool with many actions, more transparency is needed.

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 fairly long with a bullet list of 13 actions, which is necessary but could be more concise. The structure is clear but not front-loaded; the key purpose is stated first, but the list could be trimmed by removing redundant phrasing like 'List all open editor windows' for get_windows.

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?

With 8 parameters, nested objects, and no output schema, the description should explain what each action returns and how to use parameters. It only gives one-line descriptions of actions, omitting return values and parameter details. This is insufficient for an agent to use the tool correctly without additional context.

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?

Input schema coverage is 100%, with descriptions for all parameters. The tool description adds little beyond listing action names; it does not elaborate on parameter usage or the complex sceneViewSettings object. Baseline score of 3 is appropriate given high schema coverage.

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 controls Unity Editor windows and UI elements, and enumerates 13 specific actions. This distinguishes it from sibling tools like editor_selection or play_mode, which have different purposes.

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 provides no guidance on when to use this tool vs alternatives. It lists actions but does not explain when to choose this over other editor control tools or provide context for selecting specific actions.

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