sequence.keyframe_volume

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

Annotations are sparse: readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false. The description adds none of the important behavioral context that annotations lack, such as whether this creates or overwrites a keyframe, whether it modifies the fcurve or the strip directly, what happens if a keyframe already exists, or whether scene revision checks are enforced. It does not contradict annotations, but it also does not disclose the mutating nature of keyframe insertion.

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 very short, but its brevity is not value-dense. The first sentence merely restates the command name and the second sentence repeats generic policy boilerplate. It earns points for being short and front-loaded, but the sentences do not carry useful meaning.

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 there is no output schema content shown, sparse annotations, and a 7-parameter input schema in a complex Blender sequence-editing context, the description is dramatically incomplete. It does not explain what object is targeted by 'name', what happens on repeated calls, whether the tool is part of a transaction flow, or what success and failure look like.

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 of the 7 parameters, only _requestId, _authorization, and _transactionId have descriptions in the schema. The key parameters 'frame', 'name', and 'volume' have no descriptions, and the tool description adds zero meaning beyond the bare parameter names. An agent cannot know what 'name' refers to, what units 'volume' uses, or which frame indexing convention applies.

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 merely echoes the command name 'sequence.keyframe_volume' and adds generic risk and maturity information. It never states what the tool actually does, such as keyframing a sequence strip's volume property over time, so an agent cannot distinguish it from sibling tools like blender_sequence_set_volume or blender_animation_insert_keyframe.

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 versus alternatives. The description only mentions that per-request argument checks and session policy apply, which is generic harness boilerplate and does not help an agent decide between setting a volume at a given frame versus setting an absolute volume on a strip.

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