tokportal_upload_video_direct

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

Annotations indicate it's a write operation (readOnlyHint=false) and non-destructive. The description adds context about the upload method (multipart) and return value (public URL), but lacks details on file size limits, format restrictions, or whether the operation overwrites existing videos. It doesn't contradict annotations.

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?

Two sentences efficiently convey the action, method, and result. The first sentence immediately states the purpose ('Upload a video file directly'). No extraneous words; every sentence earns its place.

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 complexity (multiple sibling upload tools, no output schema), the description is adequate but incomplete. It does not explain the relationship to tokportal_upload_video, mention any file constraints, or clarify that bundle_id is required beyond the schema. For a simple upload tool with 3 parameters, it meets minimum viability but has gaps.

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 the input schema already documents all three parameters adequately. The description adds no additional parameter semantics beyond what the schema provides. Baseline of 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?

The description clearly states the action ('Upload a video file directly') and the method ('multipart/form-data') and return value ('public video URL'). However, it does not differentiate from the sibling tool 'tokportal_upload_video' (non-direct), so some ambiguity remains about when to use this specific variant.

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 is provided on when to use this tool versus alternatives like tokportal_upload_video, tokportal_upload_image, or tokportal_upload_image_direct. There is no mention of prerequisites, conditions, or scenarios where this direct upload is preferred over indirect methods.

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