sequence.add_compositor_modifier

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

No behavioral traits are disclosed beyond the command name's implication of an add operation. The annotations are all false and provide no safety profile, so the description carries the full burden, but mentions only risk level 'standard' and maturity 'L3', which are not behavioral details.

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 very short, but this is under-specification rather than conciseness. It front-loads the command name and metadata, yet every content sentence fails to explain what the tool does.

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?

For a tool with seven parametersiveness, no annotations, and no behavioral disclosure, the description is severely incomplete. An agent would not know what the operation does, what arguments mean, what side effects occur, or when to select it.

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?

The description adds no meaning to any of the seven parameters. With only 43% schema description coverage, the core parameters groupName, name, and strip are left entirely undocumented in both schema and description.

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 restates the command name in backticks and adds risk/maturity metadata, but never says what the tool does with a verb and resource. An agent cannot tell that it adds a compositor modifier to a sequence strip, and no sibling differentiation is provided.

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 offers only 'Requirements: Per-request argument checks and session policy still apply', which is generic operational boilerplate. It provides no guidance on when to use this tool versus sibling sequence/modifier tools.

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