get_clip_envelope

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

With no annotations, the description fully discloses the sampling methodology (evenly-spaced time positions because API doesn't expose breakpoints) and the return flag for missing envelopes. This is valuable beyond what the schema conveys.

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 well-structured with a brief intro, a key caveat, return behavior, and a tidy argument list. Every sentence provides necessary information without redundancy.

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 sampling tool with an output schema, the description covers the essential behavior, limitations, and parameter details. It explains what happens when no envelope exists, making the tool's behavior predictable.

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?

The description includes an 'Args' section explaining all five parameters with clear meanings, fully compensating for the schema's 0% description coverage. It even adds range and default for num_steps.

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 names a specific verb ('Sample') and resource ('automation envelope for a device parameter in a Session clip'), clearly distinguishing it from sibling tools that insert or clear envelopes. It also narrows the scope to Session clips, removing ambiguity.

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?

The description explicitly states a key limitation ('Only works for Session clips (not Arrangement clips)') and clarifies the behavior when no envelope exists. It does not name specific alternative tools, but the distinction from insert/clear siblings is evident from the verb 'sample'.

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