unity_execute_menu_item

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

With no annotations provided, the description carries full burden for behavioral disclosure. It notes the port parameter for parallel-safe routing, but does not reveal other behavioral traits such as whether the command is synchronous, if errors silently fail, or if it requires an active project. This is adequate but not comprehensive.

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, well-structured sentence that front-loads the core purpose and immediately follows with illustrative examples. Every part serves a clear function with no redundancies.

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 parameters, no nested objects, no output schema), the description is sufficiently complete. It covers the execution action, menu path format, and the optional port for instance routing, leaving no major gaps for typical usage.

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 descriptive parameter names and descriptions. The description adds value by providing concrete examples of valid menu paths (e.g., 'GameObject/3D Object/Cube'), which clarifies the expected format beyond the schema's static description.

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 by its path, with concrete examples like 'File/Save'. This specific verb+resource pairing distinguishes it from sibling tools, none of which target menu execution directly.

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 implies its usage context (triggering editor menu commands) but does not provide explicit guidance on when not to use it or suggest alternatives. It includes practical information about the port parameter for parallel instances, which helps in multi-instance scenarios.

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