set_xmp_metadata

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

No annotations are present, so the description carries the full burden of disclosing behavior. It only implies mutation via 'set' and does not mention overwriting semantics, project requirements, permissions, or reversibility.

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 short and easy to scan, but 'Premiere Pro expanded operation' is vague filler. The only concrete phrase is 'set xmp metadata,' so brevity does not compensate for missing substance.

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?

For a mutation tool with no annotations, no output schema, and an uninformative input schema, the description is far too thin. It mostly restates the tool's name and provides no invocation context, side effects, or metadata structure.

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?

The input schema is empty but allows arbitrary properties, so it provides no parameter meaning. The description also fails to name expected arguments or a metadata shape, leaving an agent unable to determine what to pass.

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 identifies the operation as setting XMP metadata in Premiere Pro, so the basic purpose is inferable. However, 'expanded operation' is unexplained and no distinction is made from related siblings such as set_metadata or get_xmp_metadata, so clarity is only moderate.

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 gives no guidance on when to choose this tool over alternatives like set_metadata or get_xmp_metadata. No usage context, exclusions, or selection criteria are provided.

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