insert_envelope_points

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

No annotations provided, so description carries full burden. It fails to disclose behavioral traits such as whether existing breakpoints are overwritten, validation of time order, or error handling. Required parameters (track, clip, device, parameter) are not mentioned.

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?

Description is short and front-loaded with purpose, then parameter format. No unnecessary words, but lacks structure for remaining parameters.

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 6 required parameters, no annotations, no output schema, the description is severely incomplete. It only addresses one parameter and ignores others, making it insufficient for proper tool usage.

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?

While the 'points' parameter is described with format, the other 5 required parameters (ctx, track_index, clip_index, device_index, parameter) are not documented in the description. Schema coverage is 0%, so description should compensate but only covers one parameter.

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?

Description clearly states the tool inserts multiple automation breakpoints for a device parameter within a clip. It uses specific verbs and resources, and distinguishes from sibling 'insert_envelope_point' by specifying multiple breakpoints.

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 on when to use this tool vs alternatives like 'insert_envelope_point' or other automation tools. No context on prerequisites or typical use cases.

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