embed_image_metadata

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

No annotations are provided, so the description carries the full burden. It discloses only that stream processing is used, which hints at memory-efficient handling of large files, but says nothing about write/mutation effects, whether the source image is modified, overwrite behavior at output_path, permissions, or failure modes.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity leaves nothing to say about behavior or usage, which sits at the edge of under-specification rather than tight conciseness.

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?

This is a mutation tool with five parameters, a nested object, no annotations, and no output schema, so the description must carry behavioral context. It omits what the tool returns, whether the source is preserved, whether output_path is overwritten, and how the three metadata schemas differ.

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 all five parameters, including the nested metadata object and the schema_type enum, are already documented in the schema. The description adds no syntax, format, or constraint detail beyond that, so the baseline of 3 applies.

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?

States a specific verb+resource (embed XMP metadata into images) plus the storage backend, so the agent knows it is a write-into-image operation. It reads clearly against read_image_metadata, but it never names or distinguishes itself from validate_metadata_schema or create_xmp_packet, which also touch metadata.

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?

There is no when-to-use guidance, no statement of prerequisites or ordering relative to siblings like create_xmp_packet or validate_metadata_schema, and no note on when this should be preferred over simply writing metadata directly. Usage is only inferred from the verb.

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