gaudio_upload_file

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

No annotations provided, so description carries full burden. It discloses multipart upload behavior, uploadId validity (72 hours), reusability across jobs, and supported formats. This is good transparency for a file upload action.

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 clearly front-loading the purpose and then adding key details. Every sentence adds value without 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?

Covers upload process, reusability, formats, and validity. However, does not explicitly state what the tool returns (e.g., uploadId). Minor gap but overall sufficient 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?

The schema already describes filePath as 'Absolute path to the local file'. The description adds context about supported formats but does not significantly enhance parameter understanding beyond the schema. 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?

The description clearly states it uploads a local audio/video/text file to Gaudio servers, with automatic multipart upload. This verb+resource combination is specific and distinct from sibling tools that deal with jobs, models, 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?

The description explains automatic multipart upload and uploadId reuse, but does not explicitly specify when to use this tool versus alternatives like gaudio_create_job. Usage is implied but not clearly guided.

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