Set Active Sequence

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

Annotations already declare the full profile (not read-only, not idempotent, not destructive, closed-world), so the bar is lower, but the description adds no context beyond them: it does not say whether this alters editor UI state, whether it persists with the project, or what happens if the name is ambiguous.

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?

One short, front-loaded sentence with no filler. It is efficient, though it is so terse that it barely differentiates itself from the title.

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?

An output schema exists so return values need not be explained, and the tool is simple with one well-documented parameter. Still, for a state-changing operation an agent would benefit from knowing the sequence must pre-exist and what side effects 'active' has; the description is minimally viable rather than complete.

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% and the single parameter is fully documented in the schema; the description's 'by name or ID' merely echoes that. Baseline 3 applies since the schema carries the semantics.

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 specific verb and resource ('Set the active sequence'), which is distinguishable from siblings like set_sequence_settings or set_sequence_frame_rate. It does not explicitly contrast with the read counterpart get_active_sequence, but the direction of the operation is unambiguous.

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, no prerequisites (e.g. the sequence must already exist in the project), and no mention of what 'active' affects for downstream calls. The agent must infer all context.

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