Premiere export

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which establishes the tool is a mutation. The description adds the term 'confirmed' which hints at an approval or validation step, but it does not specify what gets destroyed, whether permissions are required, or what the side effects are. Given the annotations cover the core destructive nature, the description adds a small amount of extra context, though it remains thin.

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, compact sentence with no fluff or redundant phrasing. It front-loads the verb and primary resource. It is appropriately sized for the amount of information it conveys, even though that information is minimal.

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?

With six parameters, nested objects, no output schema, and zero parameter descriptions, this tool is complex. The description provides only a broad purpose and fails to explain the workflow, required identifiers, confirmation process, or expected behavior. It is wholly inadequate for an agent to invoke the tool 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?

Schema description coverage is 0%, so the input schema provides no parameter meaning. The description does not compensate by explaining any parameters, such as actionId, args, target, approvalId, operationId, or expectedRevision. It only lists export types, which could relate to actionId values but not explicitly. With no parameter information anywhere, the agent cannot correctly construct a call.

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 a specific verb ('Run') and a resource ('export actions') and enumerates export types (frame, sequence, interchange, AME). It is not a tautology and clearly indicates the tool's domain, distinguishing it from other premiere tools that are not export-specific. However, it does not explain what 'confirmed' means or what constitutes an export action, so it is slightly vague.

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 offers no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the action without context about the workflow or how this tool fits among sibling tools like premiere_operations or premiere_api. The agent is left to infer usage.

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