sequencer.modifiers

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'List strip modifiers on a sequence strip,' but does not confirm it is a read-only operation, mention side effects, or describe authentication or rate limits. This is insufficient for an agent to understand the tool's safety profile.

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 concise (one sentence), but it omits critical information such as parameter semantics and output details. While brevity is valued, this is under-specification, not conciseness. It earns its place only by stating the core purpose.

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 the tool's simplicity (one parameter, no output schema), the description should explain what 'strip modifiers' are and what the output looks like. It fails to do so, leaving the agent with insufficient context to use the tool effectively. For a list operation, the absence of output schema makes the description incomplete.

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 input schema has a single required parameter 'name' with no description (0% schema description coverage). The tool description does not explain what 'name' refers to (e.g., the strip name). This leaves the agent without guidance on how to use the parameter, making it impossible to invoke correctly.

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 clearly states the verb 'List' and the resource 'strip modifiers on a sequence strip'. It distinguishes this tool from sibling tools like 'modifiers.list' (for object modifiers) and 'sequencer.modifier_add' (for adding modifiers). The purpose is specific and 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?

The description implies usage for listing modifiers on a sequence strip, but provides no explicit guidance on when to use this tool versus alternatives (e.g., when to use 'modifiers.list' for objects). No prerequisites or exclusions are mentioned, leaving room for ambiguity.

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