Premiere media

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

Annotations already communicate that the tool is not read-only and can be destructive (readOnlyHint=false, destructiveHint=true), so the description is not required to repeat that warning. However, it adds little behavioral context and does not explain what might be changed or destroyed beyond naming action categories.

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 concise: one sentence, front-loaded with the action and resource. It avoids filler, though 'typed' is jargon that could be replaced with a more useful qualifier.

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 six-parameter schema, no output schema, nested objects, and destructive annotation, the description is far too skeletal. It does not explain the actionId dispatch, target/args contract, or how this tool relates to the broader Premiere tool family.

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 schema has 6 parameters including required actionId, plus nested target/args objects, but the description mentions none of them. With schema coverage at 0%, the description provides no practical help for selecting or filling parameters correctly.

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 concrete action categories for a media resource: import, relink, proxy, and metadata. This makes it distinguishable from sibling tools like premiere_export or premiere_effects_audio, though the term 'typed' is unexplained and the specific outcome is 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?

No when-to-use guidance is provided. The description does not mention alternatives, prerequisites, exclusions, or when to prefer a different Premiere tool such as premiere_inspect, premiere_export, or premiere_capabilities. The reader must infer that it is for media operations.

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