get-photo

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

No annotations are provided, so the description must fully convey behavioral traits. It does not state that the tool is read-only or that it does not modify data, nor does it mention required permissions, side effects, or error handling. For a metadata retrieval tool, this is a significant omission.

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 a single sentence that is well-structured and front-loaded with the core action. It lists multiple metadata types efficiently, though it could be slightly more organized (e.g., grouping related fields). No redundant words.

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 simplicity and absence of output schema, the description provides a reasonable overview of output contents. However, it lacks information on error cases (e.g., missing UUID), no mention of read-only nature, and does not clarify that it is specific to Apple Photos library.

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 baseline is 3. The description adds value by detailing the metadata returned but does not enhance understanding of the parameters beyond what the schema provides (e.g., default behavior of 'library', format of 'uuid').

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?

Description clearly states the tool retrieves full metadata for a single photo by UUID and enumerates the metadata fields (dimensions, dates, location, etc.), making the purpose unambiguous and distinct from sibling tools like 'query' or 'library-info' which serve different scopes.

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 implies usage for fetching metadata of one photo, but does not explicitly clarify when to prefer this over 'query' (which likely handles multiple photos) or mention any prerequisites or exclusions. No alternative tools are referenced.

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