bittensor_video

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

With no annotations provided, description carries full burden and comprehensively discloses: async polling behavior, 3-minute timeout, return format (MP4 URL), and per-call cost. Lacks only rate limits or error handling details.

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?

Four sentences, zero waste: purpose+subnet, async timing, return format, cost. Front-loaded with primary function, every clause provides essential behavioral or cost information.

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 single parameter, no annotations, and no output schema, description adequately covers critical operational aspects (cost, async behavior, timeout, return type). Minor gap in error state documentation.

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% description coverage ('Video description to generate'), establishing baseline. Description does not add syntax details, examples, or prompt engineering guidance beyond schema definition.

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?

States specific verb ('generation') and resource ('video'), with explicit differentiation from siblings via 'Bittensor subnet 18' (distinguishing from bittensor_image, bittensor_3d, bittensor_tts, etc.).

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?

Provides clear usage context through temporal constraints ('Async — polls until ready (up to 3 min)') and cost disclosure ('$2.00 per call'), guiding when to use vs alternatives, though does not explicitly name sibling alternatives.

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