read_sequence_transcription

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

With no annotations provided, the description carries the burden. It discloses the requirement for the optional panel, the return type (timeline-timed segments plus diagnostics), and the non-support for captions. It does not mention side effects (likely none) or failure modes if the panel is missing, but for a read tool this is adequate.

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 two concise sentences: the first states the core function and requirement, the second explains the output and limitation. Front-loaded and economical, with no redundant information.

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 low complexity (1 optional param, no output schema, no annotations), the description is complete: it covers the function, prerequisites, return content, and what it does not cover. For a read-only tool, no further details are necessary.

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 100% (the single sequenceId parameter is described with 'Optional sequence ID. Defaults to the active sequence.'). The tool description does not add additional parameter semantics, but the schema already handles it fully, so the baseline 3 is appropriate.

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 clearly states the tool reads Premiere Speech-to-Text transcripts from source clips of a sequence, distinguishing it from caption reading ('it does not read caption tracks') which is a distinct sibling tool (read_sequence_captions). The verb 'Reads' is specific to a resource and scope.

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 provides a clear prerequisite (requires MCP Transcript Bridge panel in Premiere Pro 25.6+) and an explicit exclusion ('does not read caption tracks'), which guides when not to use it. However, it does not explicitly name an alternative for caption tracks, though the sibling list includes read_sequence_captions, making the guidance strong but not fully explicit.

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