batch_apply_effect

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

No annotations are present, and the description provides no behavioral information. It does not disclose whether it modifies clips in place, requires a selection, has side effects, or any other operational details, leaving the agent without critical safety or execution context.

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 brief, but this is under-specification rather than concise effectiveness. It lacks any useful structure or elaboration, making it a label rather than a helpful description.

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 that likely needs to specify an effect and target clips, the description is completely inadequate. There is no explanation of the input object, expected behavior, or output, and the combination of an open schema and no annotations makes this tool impossible to invoke correctly based solely on the description.

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 is an open object with no defined properties (additionalProperties allowed), so the agent has no structured guidance. The description adds no parameter meaning, not even hinting at what fields like 'effect' or 'clip' might be expected. With a schema coverage of 100% but effectively zero documented parameters, the description fails to compensate.

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 states the tool does 'batch apply effect', which clearly identifies the operation as batch-applying an effect. However, 'expanded operation' is vague and doesn't specify what effect, which clips, or any distinguishing details beyond the sibling 'apply_effect'. It gives a basic sense of purpose but lacks specificity.

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?

There is no guidance on when to use this tool, what selections or prerequisites are needed, or how it differs from similar tools like 'apply_effect' or 'batch_enable_disable'. No usage context, exclusions, or alternatives are provided.

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