sequence.trim

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

Annotations provide no destructive/idempotent hints Qualified, but the description adds only 'risk standard' and 'maturity L3'. It does not disclose whether trimming is irreversible, what gets modified, or any side effects, leaving the agent without behavioral context for a mutating operation.

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 short but the first sentence merely restates the title and the second provides generic risk/policy metadata. Neither sentence adds functional value, so the brevity is underspecification rather than effective conciseness.

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 mutates a sequence and involves transaction ids, authorization, and expected revisions, the description is critically incomplete. It provides no purpose, no preconditions, no effect, and no usage context, even though an output schema exists.

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 description coverage is only 43%, and the description names none of the parameters. While `name`, `frameStart`, and `frameEnd` are somewhat self-explanatory, the description adds no meaning beyond the schema and leaves `_expectedSceneRevision` and others without context.

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 command name (`sequence.trim`) and offers no verb, resource, or outcome. An agent cannot determine what trimming means, what it acts upon, or what state change it causes.

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 about when to use this tool versus the many sequence-related siblings such as blender_sequence_add, blender_sequence_move, or blender_sequence_set_speed. The note that session policy applies is not usage guidance.

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