higgsfield_generate_video

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

With no annotations, the description carries full burden. It discloses the async polling behavior (generation_id) but lacks details on authentication (api_key required but not mentioned), rate limits, or side effects. It adds moderate context but leaves gaps.

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?

Three short sentences, no fluff, front-loaded with purpose. Every word earns its place.

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 full schema, supportive sibling tools (get_styles, get_status), and no output schema, the description provides sufficient context for an agent to use the tool correctly, though it could mention the api_key requirement.

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 coverage is 100%, so baseline is 3. The description adds value by explaining that Soul Styles give 'cinematic looks' and that the return value is a generation_id for polling, which complements the schema descriptions.

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 it generates a video from a text prompt using Higgsfield AI, mentions Soul Styles for cinematic looks, and indicates it returns a generation_id for polling. This distinguishes it from siblings like higgsfield_generate_image (image) and higgsfield_get_status (polling).

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 when to use it (to generate a video) and hints at the workflow (polling with generation_id). However, it does not explicitly name alternatives or state when not to use it, though the sibling tools provide context.

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