audible_product

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

With no annotations, the description carries the burden and does add useful context: it states the data is 'Credential-free public catalog data from api.audible.com,' disclosing auth requirements and source. However, it does not disclose behavior on invalid/unknown ASINs, rate limits, or how normalization affects fields, so transparency is partial.

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 sentences, front-loaded with the action ('Get an Audible audiobook'), followed by a concise enumeration of return fields and a source/auth note. Every sentence adds value; there is no filler or repetition.

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?

For a single-parameter read tool with no output schema, the description is largely complete: it enumerates the normalized fields returned and clarifies that no credentials are needed. It lacks only minor guidance on how to obtain the ASIN and what happens when a product is not found, but these are not critical for this simple lookup.

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?

The input schema already documents the only parameter (asin: 'Audible ASIN') at 100% coverage, so the baseline is 3. The description adds no additional meaning about the parameter—it doesn't explain ASIN format, how to discover an ASIN, or constraints.

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 a specific verb+resource: 'Get an Audible audiobook,' and lists the detailed return fields, making clear this is a single-product lookup by ASIN. It does not explicitly contrast with siblings like audible_search or audible_products, but the singular resource and field list distinguish it from list/search tools.

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 use when you have an ASIN and need a single audiobook's catalog details, but it never states when to use it versus related tools such as audible_search or audible_product_reviews. No exclusions, prerequisites, or alternative routing are provided.

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