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

Beyond the annotations (which already declare readOnly/idempotent/non-destructive/openWorld), the description adds genuinely useful behavioral context: the automated checks are not a listening review, source tags are only creator hints, and callers must preserve attribution and follow each sample's licence. These caveats are not derivable from annotations or schema.

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?

Four short sentences, front-loaded with the core purpose before the cost, quality and licensing caveats. Dense but each sentence carries information; no wasted filler.

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?

An output schema exists so return values need not be described, and the description covers cost, licence/attribution policy and metadata caveats. Still, with 8 parameters at 13% schema coverage and no mention of limit/offset, an agent lacks full calling guidance, so it is only minimally complete.

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 only 13% (only 'q' documented), so the description would need to compensate. It names the searchable dimensions (keyword, pack, BPM, key, licence), partially mapping to q/pack/bpm_min/bpm_max/key/license, but gives no syntax or format detail and never covers limit/offset. Adequate but incomplete against a low-coverage 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 names a specific verb (Find) and a precise resource set (released original synthesis kits and individually auditioned source samples) plus the search facets (keyword, pack, BPM, key, licence). It is clearly a search tool, but it never explicitly distinguishes itself from the singular sibling get_open_loop, so it stops short of 5.

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?

It notes the tool is 'Free; no account or tokens required,' which implicitly contrasts it with token/paid siblings like estimate_cost, get_token_balance, purchase_token_pack and start_trial. However, there is no explicit when-to-use/when-not statement and no named alternative (e.g., vs get_open_loop), leaving usage to inference.

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