photos_list_timeline

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds valuable behavioral detail: authentication requirement, default return shape, the effect of loadDetails=true, the exact fields returned, and the fact that it buffers the whole list in memory and is slower. No contradictions with annotations.

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?

Every sentence in the description earns its place: scope, auth, default output, the loadDetails option with tradeoff, and sibling tool routing. It is information-dense without being bloated.

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 fully covers what an agent needs to call this tool correctly: what it returns by default, how to get more detail, performance implications, authentication, and related tools. With the schema and annotations also present, nothing important is missing.

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 schema already documents loadDetails well, but the description greatly enriches it by specifying the exact return shape with and without the flag, plus the performance/memory tradeoff. This goes well beyond the schema's basic boolean description.

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 ('List photos in your Proton Photos timeline') and identifies the scope as the full library, explicitly noting it is not scoped to an album. This clearly distinguishes it from photos_list_album_photos and other photo 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 provides clear context on when to use this tool and routes to related tools: photos_download for downloading items and photos_add_to_album for adding to albums. It does not explicitly name photos_list_album_photos as the alternative for album-scoped lists, but the 'not scoped to an album' phrasing makes that distinction clear.

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