list_keyframes

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

With no annotations, the description carries full responsibility for disclosing side effects. It does not explicitly state that the operation is read-only or that it does not modify the scene, leaving potential uncertainty about whether listing keyframes has any side effects.

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, concise sentence that starts with the main action. It is efficient but slightly terse; however, it covers the core purpose without unnecessary detail.

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?

Given the lack of parameter explanations and no description of the output format (despite an output schema being present), the description is incomplete. An agent would need additional information about the expected inputs and the structure of the returned keyframe data.

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?

The description does not explain the two parameters, 'object' and 'data_path', and the schema provides no descriptions (0% coverage). An agent cannot infer what values to pass, such as the object name or the property path for the fcurve, making the tool difficult to use correctly.

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 tool's function: listing fcurves and keyframes with frame, value, and interpolation. The verb 'list' and the resource 'fcurve and keyframes' are specific, and it is distinct from sibling tools like insert_keyframe or delete_keyframe.

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 explicit guidance is provided on when to use this tool versus alternatives. While it is implied that listing is the opposite of inserting or deleting, the description does not mention any conditions or trade-offs.

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