motion_list_keyframes

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

No annotations are provided, so the description carries the burden. The word 'List' implies a read-only operation, and the description discloses ordering and return fields (time, value). However, it doesn't explicitly guarantee non-mutation, discuss edge cases (e.g., missing parameter), or mention performance for large curves.

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 a single, front-loaded sentence that conveys purpose, output format, and ordering without wasted words. Every word 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?

The description adequately covers the tool's purpose and output aspects, and the existence of an output schema covers return values. However, the complete lack of parameter semantics and usage guidance for a 3-parameter tool leaves notable gaps.

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% and the description does not define any of the three parameters (path, scenenode_id, parameter_path). While the context implies parameter_path refers to the animated parameter, the description offers no explicit meaning for any parameter, leaving the agent to infer.

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 action ('List'), the resource ('keypoints on an animated parameter's curve'), and the scope ('every keypoint... in document order, with time (seconds) and value'). This distinguishes it from sibling tools like motion_list_layers and motion_list_text_layers, which list different resources.

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 when to use this tool: when you need to see all keyframes on an animated parameter. However, it doesn't explicitly mention alternatives or specify when not to use it, so it stops short of full exclusion guidance.

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