get_xmp_metadata

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

With no annotations, the description carries the full burden of behavioral disclosure. It only implies a read operation through the word 'get' and provides no detail on target context, potential errors, prerequisites, or what metadata is actually returned.

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 a single short sentence with the action front-loaded. The 'Premiere Pro expanded operation:' prefix adds little value and does not help differentiate the tool from its many sibling tools, so it is not a perfect 5.

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?

Without an output schema or annotations, this one-line description is underspecified. An agent can call it with an empty object, but cannot determine what entity's XMP metadata is being read or what the response will contain, which is a meaningful gap for a tool that has no other source of context.

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?

There are zero parameters and the input schema simply allows an empty object, so there is no parameter surface to document. The description does not need to add parameter semantics, and the baseline of 4 for a zero-parameter tool 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?

The description states the operation explicitly as 'get xmp metadata' – a clear verb and resource. It distinguishes itself from set_xmp_metadata by being the getter counterpart, though it does not specify whether the target is a clip, sequence, project, or selection.

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 given on when to use this tool over alternatives like get_metadata, get_project_panel_metadata, get_item_info, or get_clip_properties. The phrase 'Premiere Pro expanded operation' is generic boilerplate and provides no selection criteria or exclusions.

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