List albums

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

Beyond the readOnly/idempotent annotations, the description reveals important non-obvious behavior: only app-created albums are returned, user-created albums are hidden due to a scope boundary, results are ordered newest first, and pagination is required via next_page_token. These are operational details an agent needs before calling.

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 deliver the core purpose, the critical scope limitation, and the pagination instruction with no filler. The most decision-relevant information is front-loaded.

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 read-only paginated list with no required parameters, the description covers scope, ordering, a key availability boundary, and how to continue paging. The lack of an output schema is acceptable because the tool's list semantics and sibling context make its return expectations clear.

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 covers all three parameters at 100%, so the description does not need to repeat their formats. The description adds only a general pagination reminder without introducing new per-parameter meaning, matching the baseline for full schema coverage.

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 states a specific action and resource: 'List the albums this app created, newest first.' It also distinguishes itself from album-related siblings by explicitly limiting results to app-created albums and noting that user-created Google Photos albums are not visible.

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 gives clear scoping context: it should be used for app-created albums, and user-created albums are unavailable to any scope since 2025-04-01. It does not explicitly name sibling alternatives like list_shared_albums, so it stops short of full alternative routing.

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