garageband_loop_search

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

With no annotations, the description must fully disclose behavior. It states the action (show browser, set query, report results) and implies non-destructiveness, but does not mention side effects like UI state changes, permissions, or whether it waits for results. It provides moderate transparency.

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, efficient sentence with no wasted words. It front-loads the main action and includes all key details (show, set search, report results).

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 has two parameters, no output schema, and no annotations, the description covers the main purpose and outputs (filtered result counts and visible rows). It could be more precise about what 'visible rows' means, but is largely complete for a simple tool.

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%, so the description must compensate for parameter meaning. It explains 'query' as search text and 'show' as browser visibility, adding value beyond parameter names. However, it does not specify the effect when 'show' is false or the exact format of the query.

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 shows GarageBand's Apple Loops browser, optionally sets search text, and reports results. It uses specific verbs ('Show', 'set', 'report') and identifies the resource ('Apple Loops browser'), distinguishing it from sibling tools like 'garageband_library_search' and 'garageband_loop_select'.

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 usage for displaying and searching loops, but lacks explicit guidance on when to use this tool versus alternatives like 'garageband_loop_select' or 'garageband_loop_drag'. No when-not-to-use or context exclusions are provided.

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