New sequence (silent)

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

No annotations provided. Description discloses key behavior (no dialog, uses newSequence method, defaults). Does not cover error handling, permission needs, or side effects like overwriting existing sequence names. Adequate but not thorough.

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?

Two sentences, front-loaded with purpose, no fluff. Every sentence adds essential information (silence, method, default, alternative use).

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 tool simplicity (2 params, no output schema), description covers creation method, default, and parameter source. Lacks error/result info, but complete enough for straightforward usage.

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 covers 100% of parameters. Description adds value beyond schema: explains presetPath default (HD 1080p 25fps) and source (from sibling tool). Parameter semantics are clear and enriched.

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?

Description clearly states 'Create a new sequence WITHOUT any dialog, using a .sqpreset'—a specific verb and resource. It distinguishes from sibling tools like 'premiere_create_sequence' by emphasizing silence and automatic creation.

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?

Explicitly says when to use: for silent, reliable sequence creation. Mentions default format and how to override with presetPath from 'premiere_list_sequence_presets'. Lacks explicit when-not-to-use or alternatives but provides clear usage context.

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