get-photos

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

With no annotations provided, the description carries the full burden. It discloses the 50-UUID batch limit, the return structure (count, photos, notFound), and the full per-photo detail shape. It doesn't explicitly state read-only behavior or potential side-effects, but the 'get' verb implies a safe read, and the described return format is transparent.

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 moderately long but well-structured with clear 'Use when', 'Returns', and 'Do not use when' sections. Every sentence provides useful guidance; there is no filler or redundancy. Slightly longer than ideal but appropriately so for a batch tool with alternatives and return details.

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 doesn't need to detail every return field, yet it still summarizes the return shape. It covers usage context, constraints, and alternatives comprehensively. The tool is fully specified for correct selection and invocation.

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 description coverage is 100%, so both parameters (uuid, library) are already well-documented. The description reinforces that UUIDs come from query/find-duplicates and mentions the 1–50 range, but adds no new semantic details beyond the schema. Baseline 3 is appropriate.

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's function: fetching full metadata for multiple photo UUIDs in one batched call. It explicitly contrasts with get-photo (single UUID), query, and get-thumbnail, making its purpose distinct and unambiguous.

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 'Use when' and 'Do not use when' guidance, naming specific alternatives (get-photo, query, get-thumbnail) and conditions (single UUID, no UUIDs yet, viewing images). This leaves no ambiguity about when to invoke this tool.

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