list_arrangement_clips

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

No annotations are provided, so description must convey behavioral traits. It states the tool 'List' (implying read-only) and mentions return fields 'start_time, length, name, and other properties.' This adds basic context but does not explicitly confirm no side effects, permissions, or rate limits. Annotations would have helped, but given the simple nature, the description is moderately transparent.

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?

Two concise sentences with no filler. Front-loaded with the primary action and resource, followed by return details. Every sentence earns its place.

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?

Although an output schema exists (supplying return structure), the description omits the required 'track_index' parameter entirely, leaving the agent uninformed about how to specify the track. Given the simplicity of the tool (1 parameter, no nested objects), the description should have at least mentioned the parameter's role.

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 coverage is 0% (no descriptions for the single parameter 'track_index'), and the description does not explain its meaning (e.g., 0-based, which track). The description adds no value over the bare schema, failing to compensate for the gap.

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 'List all clips placed in the Arrangement View timeline for a track.' The verb 'List' and specific resource 'clips in Arrangement View' distinguish it from sibling tools like 'list_clips' (likely Session clips) and 'get_clip' (single clip).

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 versus siblings. Alternatives like 'list_clips', 'get_clip', or 'place_clip_in_arrangement' are listed but not differentiated. No explicit when-not-to-use information.

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