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

Adds context beyond annotations: clarifies nothing in the project changes despite readOnlyHint=false (explained by the exported image landing in library space), discloses latency ('takes a few seconds'), and states the connection prerequisite. The annotations already cover idempotency and non-destructiveness, so this is a solid additive layer rather than a full behavioral spec.

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?

Four short sentences, purpose first, then side effects, then latency/prerequisites, then the required prior call. No filler and no repetition of structured fields beyond what aids recall.

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?

No output schema exists, yet the description explains what comes back (an image plus its address in library space) and what must hold true before calling. Nothing an agent needs to invoke this correctly is missing.

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 coverage is 100% with both parameters documented (seconds from sequence start, uuid from premiere_list_connections). The description restates 'at a given second' and reinforces where deviceId comes from, but adds no format or boundary detail (e.g., the 0–86400 range) beyond the schema. Baseline 3 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?

States a concrete verb+resource+scope: 'See one frame of the sequence your Premiere panel shares, at a given second.' This lets an agent distinguish it from premiere_read_timeline (structure) or premiere_shot_log (logging) without inspecting schemas.

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?

Gives clear operating conditions and an explicit call sequence: panel must be open and connected, and 'First call premiere_list_connections to get the deviceId.' It does not name a sibling alternative or exclusion (e.g., when to prefer premiere_read_timeline or frame_at), so it stops short of full routing guidance.

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