set_xmp_metadata

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it discloses nothing — no side effects, no requirement to have the file selected or writable, no note on whether existing XMP data is overwritten, and no return value. The term 'expanded operation' hints at low-level behavior but never explains it.

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?

It is a single short sentence, but this is under-specification rather than conciseness. The opening phrase 'Premiere Pro expanded operation:' is wasted characters that add no value over the tool name, and the remaining text is pure tautology.

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?

In the context of a 240+ sibling tool environment with a clear get/set semantic split, this description is wholly inadequate. There's no mention of return values, relationship to get_xmp_metadata, object it operates on, or error conditions (e.g., missing metadata values). The near-total overlap between name and description means the agent gets nothing beyond the identifier.

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?

Per the rubric, 0 documented parameters earns a baseline of 4. However, this is somewhat generous: the schema is suspiciously empty (only propertyNames/additionalProperties, no actual properties), and a 'set' operation almost certainly requires arguments that are entirely undocumented in both the schema and the description. Neither source provides any meaning.

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 'set xmp metadata' is essentially a verbatim restatement of the tool name with no added meaning. The 'Premiere Pro expanded operation:' prefix provides no functional information, and there's no clarification of what XMP metadata is set on (clip, sequence, project) or what the operation does beyond the literal name.

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?

No guidance is provided on when to use this tool versus closely related siblings like `set_metadata`, `get_xmp_metadata`, `set_project_panel_metadata`, or `add_custom_metadata_field`. There's no mention of prerequisites (e.g., must a file be selected?), workflow positioning, or when not to use it.

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