Premiere effects and audio

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

Annotations declare readOnlyHint=false and destructiveHint=false; the description's 'Discover or apply' conveys both read and write behavior, which is consistent and slightly extends the annotations by signaling that some operations mutate. No contradiction. However, it discloses nothing about side effects, reversibility, or what 'apply' executes.

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 single sentence is efficient and front-loads the primary verbs. But for a tool spanning five operation categories with 6 parameters and nested objects, this reads as under-specification rather than disciplined conciseness — the brevity buys little because the content is not informative.

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 broad, high-complexity tool (6 params, nested args, no output schema, no enums, no parameter docs), the description is severely inadequate. It never explains how operations are invoked via actionId, what args/target structures look like, or what is returned. An agent cannot reliably construct a correct call.

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 description must carry the full burden for explaining parameters. It explains none of them — actionId, args, target, operationId, approvalId, and expectedRevision are all undocumented in both the schema and the description, including the two nested objects (args, target). Critical gap.

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 clear verb-resource combo ('Discover or apply ... effects, parameters, keyframes, transitions, and audio operations') that distinguishes it from media/project/export siblings. However, it is an extremely broad umbrella claim spanning five separate domains and could overlap conceptually with premiere_operations, so differentiation is weak.

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 use this tool versus any of the twelve siblings. It does not name alternatives, state exclusions, or indicate which of its many operation types should route here vs to premiere_timeline, premiere_media, or premiere_operations. An agent gets no decision support.

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