upload_drive_file

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

With no annotations, the description adequately discloses behavior: API endpoint, return values, optional Wiki attachment, and auth order ('UAT-first with app fallback'). Could be improved by mentioning file size limits or overwrite behavior.

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?

Three concise sentences covering key aspects (action, API, returns, optional behavior, auth order). No redundancy or filler.

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 no output schema, the description mentions return values (file_token + url). It sufficiently covers the tool's behavior for an upload operation, though it could elaborate on error scenarios or prerequisites.

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 all 4 parameters, but the description adds value for 'folder_token' by suggesting how to find it (use list_files) and providing an example ('我的空间' root token). This goes beyond the schema's static description.

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?

Description clearly states the action: upload a file from disk to a Feishu Drive folder, specifying the API endpoint. It distinguishes from sibling tools like 'upload_file' by focusing on Drive folders and optional Wiki attachment.

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 explicit guidance on when to use this tool versus alternatives like 'upload_file' or 'upload_image'. Mentions optional Wiki space behavior but lacks when/when-not context.

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