upload_video

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

No annotations provided. The description adds constraints (size, format) but lacks disclosure of processing behavior, rate limits, or authentication needs. It does not mention that the timeout and poll_interval parameters suggest asynchronous processing.

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 two sentences with no unnecessary words, front-loading key constraints (size, format, absolute path).

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 no output schema and no annotations, the description fails to explain return values, error handling, or the significance of timeout/poll_interval parameters. It is not fully complete for an upload tool.

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 coverage is 100% so baseline is 3. The description adds value by emphasizing the path must be absolute, but does not elaborate on timeout or poll_interval beyond the schema.

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 uploads a video file with specific constraints (max size, format) and requires an absolute path. It effectively distinguishes from siblings like upload_image.

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 implies usage for video uploads but does not explicitly state when to use vs alternatives like upload_image, nor does it mention when not to use this tool.

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