get_saved_audiobooks

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

With no annotations, the description must disclose behavior independently. It does mention the 'user-library-read' scope requirement, which is a key behavioral constraint. However, it does not describe pagination behavior beyond what the schema already covers, nor does it mention potential errors, rate limits, or the return format. For a list operation, these gaps are moderate, so a 3 is appropriate.

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 sentence that front-loads the core action and resource, followed by the scope requirement. It contains no fluff and every word contributes to the tool's purpose. This is appropriately concise for a simple list operation.

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 simple list tool with a fully documented schema and no output schema, the description provides the essential context: what it lists and the required scope. It could mention that results are paginated, but that is already implied by the limit/offset parameters. The lack of an output schema means the description might need to state what is returned (e.g., an array of audiobook objects), but this is a minor omission given the typical expectation. Overall, it is nearly complete for its complexity level.

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% for the two parameters (limit and offset), and the description adds no additional meaning about parameters. It doesn't explain how to use limit/offset or any special semantics, so it meets the baseline but doesn't exceed it.

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 identifies the verb 'List' and the specific resource 'audiobooks saved in the current user's Spotify library,' which distinguishes it from sibling tools that list other saved types (tracks, albums, shows). It precisely states what the tool does without ambiguity.

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 clear context (it's for saved audiobooks) and names a required scope (user-library-read), but it lacks explicit guidance on when to choose this over alternatives or when not to use it. It doesn't mention any exclusions or route to siblings like get_saved_tracks, but the context is clear enough for an agent to infer appropriate use.

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