hyperframes_render

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

No annotations provided, so description must fully disclose behavior. It only states the action and lists parameters, without revealing important traits like resource intensity, side effects, or whether output path overwrites. This is insufficient for a render tool.

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?

Description is front-loaded with a clear single-sentence purpose. The parameter list is structured and readable, though lengthy. It effectively organizes 25 parameters without extra fluff.

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?

While parameters are individually described, the description lacks an overall context (e.g., typical render workflow, expected output, or interaction with other params). Output schema exists but is not leveraged to explain return values.

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%, but the description compensates by giving inline explanations for each parameter (e.g., 'Absolute path to the Hyperframes project directory'). This adds substantial meaning beyond the schema's type-only definitions.

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 'Render a Hyperframes composition to video', providing a specific verb and resource. This distinguishes it from siblings like hyperframes_preview or hyperframes_validate.

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 when-to-use or alternatives guidance. The purpose is implied by the name and description, but the description does not clarify when to choose this over other hyperframes tools (e.g., still, preview).

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