upload_material

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

Discloses video transcoding to H.264 MP4, return fields, and a specific instruction (do not write FFmpeg overlay). With no annotations, it covers key behavioral traits adequately.

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?

Single paragraph that front-loads purpose and returns, then provides behavioral details. Concise but could be better structured with bullet points.

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?

With no output schema, the description lists return fields and usage tips. It references a sibling tool for additional constraints. Moderately complete, missing error handling but sufficient for common use.

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 already describes both parameters (100% coverage). The description does not add significant meaning beyond the schema; it only provides general context about the upload process.

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 images or videos to OSS and lists the return values. It distinguishes from sibling 'upload_html' by specifying different resource types.

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 recommendations (video length 5-15s, hard cap 10min) and directs to get_material_guidelines for size limits. Does not explicitly specify when not to use this tool, but context is clear.

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