set_metadata

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

With no annotations, the description provides valuable behavioral details: writes losslessly to EXIF APP1 segment, no JPEG recompression, and keywords stored as XPKeywords in UTF-16LE semicolon-separated format. However, it omits failure modes (e.g., file write errors, missing EXIF segment).

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?

Two concise paragraphs; the first sentence fronts the core purpose. Every sentence adds value (technical detail on EXIF, keyword format, param listing). No wasted 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?

The description covers main behavior adequately given 6 parameters and no annotations, but lacks details on the output (has an output schema not mentioned) and edge cases (e.g., what happens if file is not JPEG or locked). It is functional but not exhaustive.

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 0%, so the description must compensate. It lists all 6 parameters, explains the purpose of each, gives an example for copyright, and notes that keywords is a list and output_path defaults to in-place. This adds significant meaning beyond the schema's bare type definitions.

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 writes metadata (copyright, artist, description, keywords) into an exported JPEG file. The verb 'write' and specific resource 'JPEG file' are precise, and it distinguishes itself from siblings like 'strip_metadata' and 'inspect_metadata' by focusing on writing.

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 writing metadata but lacks explicit when-to-use or when-not-to-use guidance. No mention of alternatives like 'strip_metadata' for removal or 'inspect_metadata' for reading, nor any prerequisites (e.g., file must be a JPEG).

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