tokportal_upload_video

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

Beyond annotations, the description reveals important behaviors: the presigned capability is short-lived, the response contains a secret, the replay ledger never stores it, and requests with the Idempotency-Key get rejected with a specific error code before any operation. This adds significant context that annotations alone don't provide.

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?

Front-loaded with the purpose, then adds behavioral warnings. It's a bit repetitive on the Idempotency-Key point (stated twice), but otherwise concise. Every sentence adds value, though the redundancy prevents a 5.

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?

For a simple creation tool with no output schema, it explains purpose, a key constraint, and response characteristics (contains a secret, not stored). It doesn't describe the exact response structure or steps after obtaining the URL, but is adequate for the tool's complexity.

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% with the body parameter fully described. The description adds no extra meaning about parameters; it only mentions the URL creation. Baseline is 3 because the schema already documents fields, and the description provides no additional semantics.

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 it creates a video upload URL and returns a short-lived presigned capability. This distinguishes it from direct upload tools like tokportal_upload_video_direct, as it's about obtaining a URL rather than uploading directly.

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?

It provides a critical usage guideline: do not send Idempotency-Key. However, it doesn't explicitly compare to alternatives or specify when to use this over other upload methods, though the purpose implies it. The warning is specific and helpful but incomplete.

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