get-photo

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

Despite no annotations, the description lists the comprehensive metadata returned (dimensions, dates, location, etc.), implying a read-only operation. It does not explicitly state it is non-destructive, but the context strongly suggests safety.

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?

Four sentences with front-loaded usage condition, a clear list of return types, and an explicit exclusion case. Every sentence adds value without redundancy.

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 tool with two parameters and an output schema, the description covers when to use, what it returns, and when to avoid it, making it fully self-contained for correct 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 coverage is 100%, and the description adds minimal extra meaning beyond the schema. It provides context that uuid typically comes from query and hints at a default library, but no new parameter-level details.

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 a single photo's metadata using its UUID. It distinguishes itself from query by specifying it is for a single photo, not for summarizing multiple matches.

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?

Explicitly states when to use (have a UUID, want complete metadata) and when not to (missing UUID or want multiple photos), directing to query as an alternative.

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