garageband_click_ui_search

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

The description hints at behavior (searches and clicks only if unique and enabled), but does not cover error handling (multiple/no matches), waiting, or side effects. No annotations are provided, so description carries burden but is insufficient.

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 that efficiently conveys the core idea, but it omits important details. It is concise but under-specified for the complexity of the tool.

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 5 undocumented parameters, no output schema, no annotations, and many sibling tools, the description fails to provide complete context. Agent lacks information on parameter meanings, return values, and edge cases.

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 0%, and the description does not explain any of the 5 parameters (query, role, enabled_only, max_depth, allow_first). Agent must guess parameter purposes, which is highly insufficient.

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 it searches visible GarageBand controls and clicks the unique matching enabled UI element, providing a specific verb-resource-outcome. However, it does not differentiate from similar sibling tools like 'garageband_ui_search_action' or 'garageband_click_ui'.

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 like 'garageband_find_ui_elements' or 'garageband_click_ui'. The description implies usage for search-and-click, but lacks explicit context or exclusions.

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