unity_execute_menu_item

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

No annotations are provided, so the description carries the full burden. It states the action 'execute' but does not disclose side effects (e.g., changes to the editor state), permissions required, error handling (e.g., invalid menu path), or whether the operation is blocking. This is insufficient for a mutation tool.

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 a single sentence with three well-chosen examples. Every word serves a purpose, and the action is front-loaded. No extraneous 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 the tool's simplicity (two parameters, one required, no output schema), the description covers the core functionality. It lacks details on return values or error conditions, but for a command execution tool, the basic behavior is adequately described. Minor gaps prevent a 5.

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% for both parameters. The description adds value by providing examples of valid menuPath values, which goes beyond the schema's simple description. However, it does not elaborate on the port parameter (already described in schema) or any format constraints, so the addition is marginal.

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 the tool executes a Unity Editor menu command, with specific verb 'Execute' and resource 'Unity Editor menu command', and provides concrete examples of menu paths. This distinctly differentiates it from sibling tools like 'unity_select_instance' or 'unity_scene_open'.

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 does not explicitly state when to use this tool versus alternatives. While the purpose is clear, it lacks guidance on when not to use it (e.g., if the menu path doesn't exist) or prerequisites. The context of sibling tools implies it's for arbitrary menu commands, but no direct comparisons are made.

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