spraay_compute_video_generation

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

Adds behavioral info not in annotations: async operation, polling, cost. Annotations provide no extra context, so description adds useful transparency beyond them.

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 efficient sentences with front-loaded purpose. Every sentence adds value: action, models, async/cost. No redundancy.

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?

With output schema present, description covers async polling and cost. Mentions sibling tool for status. Lacks potential details like timeout, but complete enough for typical 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?

Schema has 100% coverage for 3 params. Description mentions model names but doesn't add meaning beyond schema's parameter descriptions. Baseline 3 is appropriate.

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 'Generate video from text' and lists specific models (MiniMax Video 01, Wan 2.1). Differentiates from siblings like spraay_compute_image_generation by specifying video generation.

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?

Describes async nature and polling requirement ('poll spraay_compute_status for results') and gives cost range. Implicitly indicates when to use (text-to-video) but no explicit exclusions or alternatives.

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