Get Keyframes

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

The description explicitly states this is a read operation ('Read'), which implies no side effects. It mentions the return format `[{frame, value, interp}]` and the optional clipping, providing clear behavioral expectations without annotation support.

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 sentences, each earning its place: the first states the main action and usage hint, the second details optional parameters and return format. No fluff, front-loaded with the primary purpose.

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?

With 6 parameters and no output schema, the description covers the core purpose, parameter semantics, and usage hints. It briefly mentions the return format, which is sufficient for a read-only tool. Could elaborate on return structure, but overall complete.

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 100%, but the description adds meaning by explaining the handle as an 'animated entity,' clarifying start_frame/end_frame as 'inclusive,' and distinguishing component usage for vector vs scalar tracks. This adds value beyond the schema definitions.

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 the keys on a specific animation track,' which is a specific verb-resource pair. It distinguishes itself from sibling tools like list_tracks (discovery) and delete_keyframe (mutation) by focusing on reading keyframes.

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 advises using list_tracks to discover param_id and component pairs, and notes that start_frame and end_frame clip the range. It lacks explicit when-not-to-use or alternatives, but the guidance is clear for the common use case.

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