sequencer-modifiers

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

With no annotations provided, the description must disclose behavioral traits. The verb 'List' implies a read-only operation, but it does not mention what happens if the strip does not exist, whether it returns an error, or the format of the output. It adds minimal behavioral context beyond the action.

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 a single, direct sentence with no superfluous words. It is appropriately sized for the tool's simplicity and immediately conveys the core action.

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 low complexity (one parameter, no output schema), the description is minimally sufficient but lacks details about return format, error behavior, or any prerequisites. It does not clarify whether modifiers are listed as a report or in some other structure, leaving some gaps in understanding.

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 schema has one required parameter 'name' with title 'Strip name', but schema description coverage is 0%. The description does not elaborate on the parameter's meaning, valid values, or formatting. It only indirectly implies the parameter refers to a sequence strip, which adds little value.

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 tool's function: 'List strip modifiers on a sequence strip'. It uses a specific verb and resource, and distinguishes itself from sibling tools like sequencer-modifier_add/set/remove by focusing on the listing operation.

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 is provided on when to use this tool versus alternatives. There is no mention of when to list modifiers (e.g., before modifying) or any comparison to the sequencer-report tool. The description is purely declarative without usage context.

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