get_user_saved_audiobooks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states this is a read operation ('Get') but does not mention that access_token is required, that limit/offset control pagination, or any error/edge-case behavior, providing minimal operational insight.

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 a single six-word sentence with no filler, front-loading the verb and resource. There is no redundancy or unnecessary detail, making it maximally 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?

With no output schema, no annotations, and a sparse description, the tool lacks critical invocation context: authentication needs (access_token), pagination behavior (limit/offset defaults), and the structure of the returned audiobook list. An agent cannot confidently call this tool without making assumptions.

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 0% and the description does not explain limit, offset, or access_token. While the parameter names and titles are reasonably self-descriptive, the tool description adds no meaning beyond what the schema already exposes, so an agent gains no additional clarity.

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 identifies a specific verb ('Get') and resource ('user's saved audiobooks'), and the 'audiobooks' term clearly separates it from sibling tools like get_user_saved_tracks or get_saved_content. It does not specify whether 'user' refers to the authenticated user or a profile passed in, which prevents a 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?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites such as authentication or platform context. There is no mention of pagination or access_token requirements, leaving the agent to infer usage from the tool name alone.

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