get_audiobooks

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

No annotations are provided, so the description carries the transparency burden. It states 'Get details' but does not specify which details; however, an output schema exists (as per context) which should document the response fields. The description does not contradict any annotations and adequately describes the read-only batch behavior.

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 relatively short but includes a redundant 'Args:' block that repeats parameter information already inferred from the input schema. A more streamlined version that integrates the limit and market format into the main description would be more concise.

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 existence of an output schema, the description does not need to explain return values. It covers the core functionality and parameter constraints (max 50 IDs, market format). It lacks mention of error handling or edge cases, but for a simple retrieval tool it is largely 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 0%, meaning the schema only provides types and titles. The description adds crucial semantics: 'List of Spotify audiobook IDs (max 50)' and 'ISO 3166-1 alpha-2 country code' for market. This adds meaning beyond the schema, though it could also explain that market is optional and its effect.

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 fetches details of multiple audiobooks in one call, with a specific limit of 50 IDs. This distinguishes it from sibling tools like get_audiobook (single audiobook) and get_audiobook_chapters (chapters), so the agent knows exactly what resource and action this tool covers.

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 batch retrieval (up to 50 IDs) versus the singular get_audiobook, but does not explicitly state when not to use it or mention alternatives like search. The context is clear, but additional exclusion guidance would improve the score.

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