set_keyframe

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

With no annotations, the description discloses validation requirements (non-empty strings, finite floats), the exact Houdini API calls used, and error behavior (status=error, no write). It also notes undoability. However, it doesn't detail the success return shape.

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?

Two tight paragraphs, the first sentence states purpose and key properties, second provides validation and implementation. No filler.

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 5-param tool with no output schema, it covers validation, operation, undoability, and error status. Missing success return spec and arcane 'PR 19' reference are minor 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 has 0% coverage, and the description compensates by constraining path/parameter to non-empty strings and frame/value to finite floats, and explaining value conversion via hou.Keyframe. Ctx remains unexplained, so not a 5.

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?

Description clearly states 'single keyframe write' with a specific verb and resource, distinguishing it from the sibling set_keyframes tool. It also notes it's scene-scoped and undoable.

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 a single keyframe but does not explicitly compare to alternatives like set_keyframes or state when to use this over other parameter-set tools. No exclusions listed.

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