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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower, yet the description still adds real behavioral context: the images themselves are not returned, only metadata, and a specific permission is required. It does not mention pagination or ordering beyond 'most recent'.

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 sentences, front-loaded with the resource and scope, then the constraint that images stay in the app and the permission requirement. No filler and nothing redundant with the title.

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?

No output schema exists, so the description carries the return-value burden and does it well: it tells the agent what fields each item yields (scene, finished, timestamp) and what is deliberately absent (image data). Permission prerequisite is also covered, leaving no gap for a one-parameter read tool.

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?

Only one parameter exists and the schema documents it fully at 100% coverage (limit, default 10, max 25), so the schema does the work. The description adds no meaning about the limit's effect on the result set, which is the baseline-3 outcome for high-coverage schemas.

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?

States a specific resource and scope: most recent photos generated on this account, plus the shape of what each entry contains (scene, completion status, time). It implicitly separates itself from search-style siblings like find_scene/find_video, but never names an alternative explicitly.

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 one useful prerequisite — the 'photos:read' permission — but gives no when-to-use condition or comparison against siblings such as find_scene, see_examples, or find_video. Usage is implied by the account-scoped framing rather than stated.

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