unity_execute_menu_item

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

No annotations exist, so description carries full burden. It clearly states the tool executes a menu command via path, implying it triggers an action. It does not detail side effects or permissions, but the action is straightforward for a menu command.

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 sentence with parenthetical examples. Extremely concise, no wasted words, front-loaded with the verb 'Execute'.

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 the tool's simplicity (2 params, no output schema), the description is complete enough. It covers purpose, parameter semantics, and provides examples. Minor gap: no mention of return value or error cases, but for a command execution tool, this is acceptable.

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%. The description adds value by explaining menuPath as a full menu path with examples and port as target instance with a hint to get from unity_select_instance and warning about parallel-safe routing.

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 executes a Unity Editor menu command by path, with concrete examples (e.g. 'File/Save', 'GameObject/3D Object/Cube'). This distinguishes it from sibling tools like unity_execute_code or unity_editor_state.

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 explicitly provides when-to-use context (executing menu commands) and includes example paths. It does not explicitly mention when not to use or alternatives, but the examples imply standard menu navigation.

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