search_audiobooks

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

With no annotations, the description carries the behavioral burden. It discloses the HTTP method (GET), the underlying API call pattern, the market limitations, and the quota tier. For a read-only search tool this is meaningful transparency beyond what the schema provides.

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?

Three short sentences, each earning its place: scope, market constraint, and quota. The most important differentiator ('audiobooks only') is front-loaded. No redundant or filler wording.

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 schema covers all parameters and the description adds endpoint, scope, market, and quota context, the tool is adequately specified for invocation. There is no output schema, but for a search tool the return shape is largely implied; the missing piece is only a bit more detail about result behavior, which is not critical here.

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 100%, so the baseline is 3. The description adds genuine value by explaining which markets support audiobooks, which directly informs how to set the market parameter. This goes beyond the schema's bare 'ISO 3166-1 alpha-2 country code' description.

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 opens with 'Search audiobooks only', which is a specific verb + resource and immediately distinguishes this tool from general search and other search_* siblings. It also names the exact endpoint and query type, leaving no ambiguity about what the tool targets.

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 phrase 'audiobooks only' gives clear context for when to choose this over general search or track/artist/album search variants. It also adds the market restriction, which is a practical usage condition. It does not explicitly name alternatives or say when not to use it, but the scope is clear enough for an agent to route correctly.

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