upload_temp_media

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

The description adds no behavioral detail beyond what the name and annotations imply. It does not mention expiration, size limits, path requirements, or side effects; annotations only provide readOnlyHint=false and destructiveHint=false, so the agent gains no additional lifecycle or safety context.

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?

One short sentence, no repetition, front-loaded with the action and resource. Every word adds meaning and the description is appropriately sized for the tool's simplicity.

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 two-parameter tool, the core purpose is clear, but the missing parameter semantics and usage context mean an agent may not know how to fill file_path or choose between temp and permanent media tools. The output schema exists, so return-value handling is not a gap.

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 0%, so the description must compensate. It partially defines media_type by listing four allowed values (images, voice, video, thumbnail), but file_path is left entirely unspecified. This is only partial compensation for the missing schema descriptions.

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 states a specific action ('上传' = upload) and a clear resource ('临时素材' = temporary media), and enumerates accepted media types (image, voice, video, thumbnail). It is clear, though it does not explicitly contrast with sibling upload tools like upload_video_material or upload_voice_material.

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 on when to use this tool versus alternatives such as permanent material uploads or download_temp_media. It neither names alternatives nor provides selection conditions, leaving the agent to infer from the '临时' (temporary) wording.

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