ui_menu_tree

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

Discloses the two modes of operation (listing top-level menus and menu items). No annotations provided, but the description is transparent about the tool's read-only exploratory behavior, though it doesn't explicitly state it's non-destructive.

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?

Three sentences: purpose, usage explanation, and practical advice. No unnecessary words; well-organized and front-loaded.

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?

Covers usage and relationship to sibling ui_menu_click. Lacks detail on return format (e.g., list of strings), but for a simple listing tool with one optional param, it is largely sufficient.

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?

With 0% schema description coverage, the description adds meaning by explaining the default null behavior yields top-level menus and providing a string yields items. It omits specifics like case sensitivity but compensates with practical usage context.

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 lists Resolve's menus or items inside a menu, and it distinguishes itself from sibling tool ui_menu_click by advising to use this tool to find an exact path before clicking.

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?

Explicitly explains when to call with no argument for top-level menu names and with a name for its items. Also advises to use this before ui_menu_click, providing clear alternatives.

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