sequence.add

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

Annotations are all false (not read-only, not idempotent, not destructive), leaving the description to carry the burden of behavioral disclosure. It does not describe side effects, state changes, or requirements. The risk/maturity boilerplate is not tool-specific and does not aid behavioral understanding.

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 extremely short, but it is under-specified rather than concise. It contains no substantive information beyond a command reference and generic boilerplate, so it fails to earn 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 14 parameters, an output schema, and a complex domain (adding various sequence strip types), the description provides no context about return values, prerequisites, or interaction with the Blender VSE. It is completely inadequate for an agent to call this tool correctly.

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 only 21%, with descriptions only for harness-internal parameters (_requestId, _authorization, _transactionId). The description adds no meaning to functional parameters like `type`, `channel`, `frameStart`, or `name`. Given the low coverage, the description should compensate but does not.

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 only restates the tool name as a command (`sequence.add`) without stating what it does. It lacks a verb-resource relationship and provides no distinction from sibling sequence tools like `blender_sequence_move` or `blender_sequence_trim`. An agent cannot infer the tool's function from the description alone.

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 guidance on when to use this tool versus alternatives. It does not mention adding sequence strips, nor does it contrast with related tools. The generic 'session policy' note offers no actionable selection criteria.

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