file_upload

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

Description lacks details about permissions, side effects (e.g., overwrite behavior), or rate limits. With no annotations provided, the description carries full burden but only mentions a size constraint.

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, front-loaded purpose, then constraint. No redundant information. Every sentence adds value.

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?

Despite low complexity, the description is incomplete. No output schema, no annotations, and missing return value, error handling, or confirmation of success. For a write operation, more context is needed.

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 67% (2 of 3 params have descriptions). Description adds the 50MB size limit for content_base64, which is valuable beyond schema. However, the 'id' parameter lacks any semantic context.

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 'Upload a file into a VM', using a specific verb and resource. It distinguishes itself from sibling file operations like fs_write and browser_open by focusing on VM file upload.

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 vs alternatives. For example, it doesn't clarify how file_upload differs from fs_write or whether it requires certain VM states. Only implied usage by name.

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