start_video_generation

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only mentions 'sin timeout', but lacks critical details such as whether the operation is async, what side effects occur, or if it is idempotent. The multi-step nature is hinted but not expanded.

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 efficient sentence conveying the action, resource, and a notable behavior (no timeout). The 'NUEVO:' prefix is unnecessary but does not harm conciseness. Information is front-loaded.

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 tool has three parameters, no output schema, and no annotations, the description should provide more comprehensive context. It fails to explain what Hedra is, what the output of step 1 is, or how subsequent steps relate. The workflow is vaguely indicated as '3 steps' but not elaborated.

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 100%, so each parameter is already documented. The tool description adds no additional meaning or context for the parameters. Baseline score of 3 is appropriate as the schema carries the information.

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 action 'Inicia generacion de video en Hedra' (start video generation) and identifies the resource as Hedra, with a note that it is the first of three steps. This verb+resource structure effectively distinguishes it from sibling tools like check_video_status or generate_complete_foxbrizio_video.

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 offers no guidance on when to use this tool versus alternatives. It labels itself as 'Paso 1 de 3' but does not explain what the other steps are or when to prefer this over generate_complete_foxbrizio_video. No prerequisites or exclusions are mentioned.

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