get_video_variation

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

The description only says 'poll', which implies repeated calls, but does not disclose polling behavior (e.g., whether it's blocking, expected call frequency, error handling, or when to stop polling). No annotations are provided to fill the gap.

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 sentence, making it concise, but it is too brief to be fully informative. It could be restructured to include key behavioral details without adding many words.

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 lack of output schema and the simple polling nature, the description should explain what the tool returns (e.g., status, result URL) and how to interpret the response. The current description is insufficient for an agent to use correctly.

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 input schema provides full descriptions for both parameters (100% coverage), linking them to generateVideo outputs. The description adds no further parameter information, so the baseline score of 3 applies.

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 states the tool polls a video generation job and indicates it's step 3 of 3, which gives some context. However, it does not explicitly state that it retrieves the result or status, leaving ambiguity about what 'poll' means exactly.

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 guidance on when to use this tool versus alternatives. The phrase 'step 3 of 3' implies it follows another step, but no explicit reference to generate_video or other tools. No mention of when not to use it or what prerequisites are required.

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