get_keyframes

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

No annotations are provided, so the description carries the full behavioral burden. It only says 'get all keyframes' and does not disclose the return format, empty-result behavior, whether the parameter must be animated, or any error conditions. Non-destructiveness is only implied by the word 'get.'

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 brief and front-loaded with the core purpose. The Args block is redundant with the schema but does not bloat the definition. It earns its place as a readable summary.

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?

For a simple two-parameter read tool, the description is minimally viable: it identifies the target resource and the required arguments. However, with no output schema and no annotations, it omits any indication of what a keyframe entry looks like or what happens when no keyframes exist, leaving some ambiguity 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?

The Args section merely repeats the schema titles ('Node Path', 'Parameter Name') without adding meaningful details. Since schema description coverage is 0%, the description should compensate by explaining path syntax (e.g., '/obj/geo1') or how to name the parameter (e.g., 'tx'), but it doesn't.

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 states a specific verb and resource: 'Get all keyframes on a parameter.' The read intent is clear and naturally distinguishes it from set_keyframe, set_keyframes, and delete_keyframe siblings, though it doesn't explicitly contrast with them.

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?

There is no guidance about when to use this tool versus alternatives. It doesn't mention set_keyframes, delete_keyframe, or get_parameter, and provides no context such as 'use this to inspect animation curves before editing.'

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