Get Keyframes

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the agent knows it is safe and idempotent. The description ('Query keyframes') aligns with these annotations and adds no further behavioral context. With annotations providing strong coverage, the description is adequate and consistent.

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 front-loads the primary action and scope. Every word is meaningful and no redundant information is present.

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 presence of an output schema (context signals: 'Has output schema: true'), the description does not need to document return values. The description covers the key aspects: node, attributes (implied), and optional time range. The complexity is low, and the description is complete for the tool's purpose.

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 100% (each parameter has a description). The description summarizes the parameters but does not add meaning beyond what the schema provides. Baseline of 3 is appropriate given high schema coverage.

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 'Query keyframes for attribute(s) on a node within optional time range.' It uses specific verb 'Query' and resource 'keyframes', distinguishing it from siblings like 'animation.set_keyframe' (creates) or 'animation.delete_keyframes' (deletes).

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 usage for retrieving keyframe data but provides no explicit guidance on when to use this tool versus alternatives. For example, no mention of prerequisites or when to prefer it over 'animation.get_time_range' or other read tools.

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