get_clip_automation

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

Without any annotations, the description should disclose behavioral traits such as side effects, authorization needs, or return format. It only states 'Get automation data' but fails to specify whether it's safe, what data is returned, or any limitations.

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 extremely concise: a single introductory sentence followed by a succinct list of parameter descriptions. Every part is necessary and 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?

Despite having no output schema, the description does not explain what 'automation data' entails (e.g., format, structure). It also omits context like whether the clip must exist or how it relates to set_clip_automation. This leaves gaps for the agent.

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?

With 0% schema description coverage, the description adds meaningful explanations for each parameter: 'The index of the track,' 'The index of the clip slot,' and 'Name of the parameter to get automation for.' This adds value beyond the schema's type/title only.

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 'Get automation data for a clip parameter,' specifying the verb (get) and resource (clip parameter). This distinguishes it from sibling tools like set_clip_automation or clear_clip_automation.

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 is provided on when to use this tool versus alternatives like set_clip_automation. The description lacks context about prerequisites or when not to use it.

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