get-photos

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

With no annotations, the description adequately conveys the tool's behavior: it is a batched read operation (max 50 UUIDs), returns detailed metadata including exif, score, detectedText, and notFound errors. It implicitly suggests no side effects, though could explicitly state read-only. Overall good transparency.

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 concise, with front-loaded usage guidance and no wasted words. The second sentence is somewhat long but packed with useful detail. It earns its place.

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?

Given the output schema exists, the description adequately covers return shape and usage context. It explains what photos includes (exif, etc.) and notFound behavior. Missing explicit error handling or rate limits, but sufficient for a batch 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?

Schema coverage is 100%, and the description adds valuable context: uuid usage from query/find-duplicates, library defaults, and batch constraint (max 50). This enhances understanding beyond the schema 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 retrieves full metadata for multiple photo UUIDs, using specific verbs and resources. It explicitly distinguishes from siblings like get-photo, query, and get-thumbnail, providing clear differentiation.

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 explicit when-to-use (several UUIDs) and when-not-to-use conditions, including specific alternatives (get-photo, query, get-thumbnail). This offers clear guidance for tool selection.

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