get-photo

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

With no annotations provided, the description discloses detailed behavior: full return list, null handling (EXIF, ML intelligence on older macOS), conditional fields (iCloud social data only for shared assets), and the burstPhotos parameter effect. It also notes the absence of side effects implicitly as a read operation.

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 longer than minimal, but the structure is logical: conditions, output details, parameter tip, and exclusions. Each sentence adds necessary information. A slight trim could improve conciseness without losing value, hence not a 5.

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 tool's complexity (many return fields, nulls, conditional data) and the presence of an output schema, the description still thoroughly explains return categories and usage constraints. It fully arms the agent with all needed context 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?

Although schema coverage is 100%, the description adds value: uuid is noted as 'typically from query', and burstPhotos is explained as listing 'sibling frames' and being empty when not a burst member. This enriches the schema descriptions with practical usage nuance.

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 purpose: retrieving complete metadata for a single photo identified by UUID. It explicitly contrasts with get-photos (multiple UUIDs) and get-thumbnail (image display), making the resource and action 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 opens with 'Use when' and closes with 'Do not use when', providing explicit conditions and naming alternatives (query, get-photos, get-thumbnail). This gives the AI agent clear decision criteria for tool selection.

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