garageband_menu_map

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

No annotations provided, so description carries burden. It explicitly states recursion and the data returned (paths, enabled state, child counts), implying read-only access. However, it does not mention idempotency or potential side effects, but 'list' suggests no modification.

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 that is clear and front-loaded. No redundant words; every part adds value.

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?

Missing parameter explanations and output format. Given 3 parameters and many sibling tools, more detail is needed to guide correct use, such as how child counts are reported or default behavior of top_menu.

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 description coverage is 0% for all 3 parameters. The description does not explain what 'enabled_only', 'max_depth', or 'top_menu' mean or how they affect output. For a tool with no output schema, this is a critical gap.

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?

Description clearly states the tool recursively lists GarageBand menu paths with details like submenu paths, enabled state, and child counts. It distinguishes from sibling tools like garageband_list_menus and garageband_find_menu_items.

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 garageband_list_menus, garageband_find_menu_items, or garageband_click_menu. The description lacks context for choosing among menu-related siblings.

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