get_xmp_metadata

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

There are no annotations, so the description carries the full burden of disclosing behavior. It only states 'get xmp metadata' with no indication of return value, potential errors, or side effects. Even the read-only nature is implied only by the word 'get' rather than explicitly stated.

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 extremely short but under-specified. It is not a well-crafted concise summary; it is a fragment that repeats the tool name. The phrase 'Premiere Pro expanded operation' is filler and provides no structural value.

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?

Given the lack of annotations and output schema, the description should provide more context about what XMP metadata is and how it is used. It fails to explain the tool's purpose within the larger set of metadata-related operations, leaving the agent without enough information to select or invoke it correctly.

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 tool has no parameters, and the schema shows 100% coverage with an empty object. According to the guidelines, a zero-parameter tool receives a baseline of 4, and the description does not need to add parameter-level detail because none exist.

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 'Premiere Pro expanded operation: get xmp metadata' essentially restates the tool name, adding only the vague phrase 'expanded operation.' It does not specify what entity the XMP metadata belongs to (e.g., a clip, sequence, or project item), making it difficult to distinguish from siblings like get_metadata or get_clip_properties.

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 alternatives (e.g., get_metadata or set_xmp_metadata). The description gives no context about the intended use case, prerequisites, or selection criteria.

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