garageband_library_search

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

With no annotations, the description carries full burden. It discloses the main actions (show, set search, list), but does not say if setting search text modifies UI state permanently, whether it's read-only, or any side effects. Lacks details on permissions or response behavior, but the core behavior is outlined.

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 efficiently conveys the core purpose. No wasted words, though it could be more structured. Front-loads the main action. Appropriate length for a simple 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?

Given no output schema and 4 parameters with 0% schema coverage, the description is too minimal. It doesn't explain how results are returned, the format, or what 'visible Library results' means. Incomplete for an agent to use effectively without additional context.

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 description must compensate. It explains 'query' as search text and implies 'limit' and 'result_depth' relate to listing results, but not explicitly. The 'show' parameter is completely unmentioned. Adds some value but not enough to fully cover the 4 undocumented parameters.

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 the Library, optionally sets search text, and lists results. The verb 'Show' and resource 'GarageBand's Library' are specific. While it doesn't explicitly distinguish from siblings like garageband_library_select or garageband_loop_search, the purpose is clear and distinct enough for most agents.

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. No context on prerequisites or when not to use. The only hint is 'optionally', which is insufficient for an agent to decide between this and sibling search/select tools.

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