get_keyframes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to specify whether retrieving keyframes is a read-only operation, what happens if the property has no keyframes, or any side effects. It doesn't describe the response format or data structure returned.

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 short sentence, which is concise, but the terseness leads to under-specification. It could be front-loaded with a clear verb and object, but lacks necessary context.

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 complexity of the tool (5 parameters, many sibling tools, no output schema), the description is too sparse. It does not explain return values, error conditions, or how parameters relate to each other, making it incomplete for effective use.

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%, so the description must compensate. It only mentions 'property' implicitly but does not explain the roles of compId, compName, layerName, layerIndex, or property. An agent would not know how to uniquely target a property without guidance on which combination of parameters to use.

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 retrieves keyframes from a property, which is a specific verb-resource combination. However, among siblings like set_keyframe, copy_keyframes, and offset_keyframes, the description could better differentiate itself by mentioning it's read-only versus the others that are write or manipulation operations.

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 guidance on when to use this tool versus alternatives like get_expression or the many other keyframe-related tools. There is no mention of prerequisites (e.g., the property must exist and have keyframes) or when not to use it.

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