garageband_wait_ui

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

The description mentions waiting for a visible element but does not disclose behavior on timeout, what the tool returns (e.g., element or boolean), or whether it polls indefinitely. With no annotations, the description should provide more details on these aspects.

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, which is concise but too brief for a tool with 7 parameters. It lacks necessary details and is under-specified for effective use.

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 7 parameters, no output schema, and no annotations, the description is highly incomplete. It does not cover return value, timeout behavior, or parameter semantics, making it insufficient for an agent to use correctly.

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%, yet the description only vaguely references 'query'. It does not explain parameters like role, enabled_only, max_depth, timeout_seconds, interval_seconds, or limit. The description fails to add meaning beyond the schema.

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 waits for a visible GarageBand accessibility element matching a query. The verb 'Wait' and resource 'GarageBand Accessibility element' are specific, and it distinguishes from sibling tools like garageband_find_ui_elements or garageband_click_ui that do not have a waiting behavior.

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. Missing context such as 'Use this to ensure an element is present before interacting, instead of garageband_find_ui_elements which returns immediately' or 'Use this when you need to wait for an element to appear after an action'.

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