sequence.transition

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

Annotations indicate this is not read-only and not idempotent, but the description adds no concrete behavioral detail such as side effects, prerequisites, or what gets mutated. 'Risk: standard; maturity: L3' is generic metadata, not behavioral transparency.

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 brevity results from omitting essential functional information. The included sentences about risk, maturity, and requirements are generic and do not justify their place in a tool definition meant to guide correct invocation.

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?

With 9 parameters, low schema coverage, and no behavioral explanation, the definition is far from complete. The presence of an output schema does not compensate for the lack of purpose, parameter semantics, and usage context.

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 33%, covering only the harness metadata parameters. The description does not explain the core parameters like first, second, channel, name, or transitionType, nor the meaning of CROSS, GAMMA_CROSS, WIPE, or SOUND_CROSSFADE.

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 as 'PartMe Blender Harness command `sequence.transition`' and adds generic risk/maturity metadata. It never states what the tool does, what resource it operates on, or how a transition is created or applied.

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 sibling sequence tools. The only usage-related sentence is a generic policy reminder about argument checks and session policy, which does not help an agent choose between alternatives.

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