get_clip_parameter_envelope

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the specific scoping to Session clips and exact beat positions, but does not disclose return format or any limitations beyond that. It is consistent with annotations.

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?

A single, concise sentence that clearly states the core function. No wasted words, and the key information is front-loaded.

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?

The description is adequate for a read tool with annotations covering safety, but lacks mention of return values (since no output schema) and does not clarify whether Arrangement clips are supported despite the schema allowing them. The scoping to Session clips is explicit but may conflict with broader schema flexibility.

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 100%, so parameters are well-documented. The description adds minimal extra meaning, only reinforcing that sampling occurs at exact beat positions, which is already captured in the sampleTimes description. No additional value beyond the schema.

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 clearly states the tool samples a Session clip parameter envelope at exact beat positions, with a specific verb and resource. It distinguishes itself from the sibling set_clip_parameter_envelope by indicating a read operation.

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 implies usage for reading envelope values but does not explicitly mention alternatives or when not to use it. Given the existence of set_clip_parameter_envelope, a note directing agents to use that for writes would be helpful, but it is not included.

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