game_ui_menu

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

Annotations are minimal (only title), so description carries the burden. It only says 'add/remove/get menu items' without disclosing side effects, required node existence, error handling, or behavior for invalid actions. No mention of destructive or safe operations.

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 extremely short (one line) and to the point. It front-loads the target node type. While it could include more detail, it avoids verbosity and is easy to parse.

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 6 parameters, no output schema, and sparse annotations, the description is insufficient. It does not explain the action enum values, return data for get_items, or example usage. An agent would need to infer behavior from the schema alone.

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%, so baseline is 3. The description adds no parameter meaning beyond the schema's property descriptions. However, it does not explain how parameters interact (e.g., which params are needed for each action), missing an opportunity to reduce ambiguity.

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 states the tool operates on PopupMenu/MenuBar nodes and performs add, remove, and get menu item actions. It is clear and specific, but does not explicitly differentiate from sibling tools like game_ui_popup, though the context implies distinction.

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 guidance on when to use this tool versus alternatives such as game_ui_popup, game_ui_control, or other UI manipulation tools. The description lacks any 'when to use' or 'when not to use' information.

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