Read Sequence Captions

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds a non-obvious behavioral caveat: empty results are not proof that the sequence has no captions because most CEP builds expose caption creation but not caption reads. This is valuable diagnostic context beyond the annotations.

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 sentences with zero filler. The first sentence front-loads the diagnostic purpose, and the second sentence adds a critical caveat about interpreting empty results, which earns its place.

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 an output schema available, return values need not be explained, and annotations cover safety traits. The description sufficiently covers the diagnostic intent and the key behavioral caveat, though it stops short of explicit usage routing among sibling tools.

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%, and the single sequence_id parameter is fully documented in the schema as an ID or name defaulting to the active sequence. The description adds no parameter semantics beyond what the schema already provides, so the baseline of 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 states a specific diagnostic verb and target: checking whether the active Premiere scripting host can enumerate caption tracks. It implicitly distinguishes from caption creation by noting most CEP builds expose creation but not reads. However, the stated purpose is more diagnostic than the tool name 'read_sequence_captions' might imply.

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 explicit when-to-use or when-not-to-use guidance and names no alternatives among the many caption-related siblings. It implies the tool is for diagnosing caption enumeration capability, but does not tell the agent when to choose it over create_caption_track or other caption tools.

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