set-photo-metadata

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

No annotations provided, but description fully discloses: it's a WRITE tool requiring environment variable, metadata-only modification, empty string clears fields, photo validation, AppleScript dependency, and return structure with before/after values for revertibility.

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?

Well-structured with labeled sections (Use when, Do not use, Safety). Every sentence serves a purpose, no fluff. Front-loaded with use guidance.

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 complexity of a write tool with 4 parameters and security implications, the description covers all necessary context: enabling writes, permissions, behavior details, and output explanation. Complete even with output schema present.

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%, but description adds crucial semantics: only passed fields are modified, empty string clears title/description, and explains return fields (uuid, updated, before/after) enabling revert. This goes beyond schema.

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 sets a photo's title, description, or favorite flag. It uses specific verbs and resources, and distinguishes from siblings like set-keywords and get-photo.

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?

Explicit 'Use when' and 'Do not use when' sections with concrete scenarios (captioning, marking best shot) and direct references to alternative tools (set-keywords, get-photo).

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