get_clip_properties

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

With no annotations, the description carries the burden. It discloses 'Read' as a non-destructive action and adds the key behavioral detail that audio-only properties are omitted for MIDI clips rather than failing. Missing error handling or permission requirements, but this is reasonable for a simple getter.

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 well-structured: purpose first, then scope, a behavioral note, and parameter definitions. Every sentence earns its place with no filler.

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 output schema covers return values, while the description explains the property scope, the MIDI omission behavior, and the parameter meanings. Minor gaps around invalid indices or error handling, but overall complete for a straightforward read tool.

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%, but the description explicitly defines both parameters with 1-based indexing and semantic labels ('Track number', 'Clip slot number'), which goes beyond the schema's bare titles. This fully compensates for the schema 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?

The description clearly states 'Read a Session clip's Clip-panel properties' with a specific verb and resource, and lists the covered properties (Transpose, Clip Gain, etc.). This distinguishes it from sibling tools like get_clip_notes or set_clip_property.

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 through the property list but provides no explicit when-to-use or when-not-to-use guidance, nor does it reference alternative tools like set_clip_property. The behavioral note about MIDI clips is useful but not a usage directive.

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