set_montage_blend

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

With no annotations, the description must disclose side effects and behavioral traits. It simply says 'set' without stating whether the modification persists, requires specific permissions, or affects existing blend settings. The mutation nature is implied but not detailed, which is a significant gap for a write 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 compact and front-loaded, with a summary line followed by a clear args list. Every line adds value, and the format is scannable. It loses a point for being sparse but not wordy.

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 lack of annotations and the write nature of the tool, the description omits return behavior, prerequisites (e.g., the asset_path must refer to a montage), and clarification of blend_out_trigger. The optional parameters' defaults are only in the schema, not described, leaving the tool under-specified for an agent.

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 0%, so the description must compensate. It provides one-line explanations for each parameter, adding units for blend times and clarifying asset_path as an Unreal path. However, blend_out_trigger remains ambiguous, and no defaults or optional semantics are explained beyond what the schema already provides via titles.

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 opens with 'Set montage blend settings,' which clearly identifies the action and resource. The parameter list further specifies that it modifies blend in/out times and auto blend out. However, it does not differentiate from sibling set_* tools or montage getters, so it stops short of a 5.

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 like set_rate_scale or get_montage_info. The description only states what it does, not the context or exclusions, leaving the agent to infer usage from the tool name.

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