list_albums

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

The description indicates this is a read-only operation (listing), but provides no details on pagination behavior, rate limits, or side effects. Without annotations, it partially carries the burden but misses some behavioral aspects like how page/per_page parameters affect results.

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?

Two concise sentences. The first sentence states the purpose and return fields; the second provides a usage hint. No redundant information, front-loaded with key action.

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?

The description covers the main purpose and return fields, and with an output schema present, it doesn't need to detail every return field. However, it omits mention of pagination even though the parameters imply it, which could be clarified for completeness.

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% (no parameter descriptions), and the tool description does not mention the 'page' and 'per_page' parameters or explain how they control pagination. The description adds no value beyond the schema, leaving agents to infer meaning from parameter names alone.

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 'List the authenticated user's albums' with a specific verb and resource. It also differentiates from sibling tool 'list_album_photos' by noting it returns summary fields (id, title, photo count, primary photo id) and suggests using the sibling for drilling into a specific album.

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?

Provides guidance on when to use this tool versus the sibling 'list_album_photos' for drilling into an album's photos. However, it does not explicitly mention alternatives like 'search_photos' or discuss limitations, though the context is clear enough for a simple listing tool.

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