generate_video

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

Annotations indicate readOnlyHint false, confirming a write operation. The description adds behavioral context: the tool requires an API token and is slow, which is valuable beyond the annotations. It does not detail other traits like rate limits or side effects.

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 extremely concise, consisting of two short sentences that each serve a clear purpose: stating the tool's function and providing a critical usage guideline. No extraneous content.

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?

Despite the tool's complexity (11 parameters, no output schema), the description offers minimal context beyond basic purpose and a usage warning. It lacks explanations of parameters, return values, authentication specifics, or behavior under different conditions, 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?

The description provides zero information about the 11 parameters; they are only defined in the schema with 0% coverage. The token requirement is mentioned but not as a parameter. The description fails to help the agent understand parameter meaning or relationships.

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 generates an AI video using LemGen, distinguishing it from sibling tools like generate_image. The verb 'generate' and resource 'video' are specific and unambiguous.

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 warns that videos are slow and should only be called after explicit user confirmation, providing clear context for when to use the tool. It does not explicitly mention alternative tools for quick tasks, but the guidance is sufficient.

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