apple_books_audiobook

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

With no annotations, the description discloses return fields (narrator, duration, audio preview) and the conditional cross-link to the ebook edition. It also notes 'from Apple Books' public catalog page' and 'normalized', implying read-only behavior. It lacks error-condition details but adds meaningful context.

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 two sentences, front-loaded with the main verb, and each sentence adds value. No filler or redundancy.

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?

Without an output schema, the description adequately itemizes expected return data and the conditional cross-link. It could mention how to obtain the ID or link to search, but for an ID-based detail tool it is sufficiently 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 description coverage is 100%, so the parameters id, lang, and country are already fully documented. The description adds no parameter-specific semantics, leaving it at the baseline of 3.

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?

Description uses specific verb 'Retrieve' and resource 'Apple Books audiobook details', clearly distinguishing from siblings like apple_books_audiobook_search or apple_books_book. The mention of 'normalized audiobook metadata' adds further specificity.

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 clearly implies use when audiobook metadata is needed, but does not explicitly name alternatives or state when not to use. This is a clear context without exclusions, appropriate for a simple retrieval tool.

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