upload_file_content

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

No annotations are provided, so the description carries the burden. It discloses the prerequisite (metadata must exist), but does not describe what happens on success, failure, or whether the upload is overwriting or appending. No return type is mentioned, and there is no output schema to compensate.

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 concise sentences with the main action in the first sentence and a key usage note in the second. No fluff or repetition of schema details.

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 simple 3-parameter upload with no nested structures and full schema coverage, the description is mostly complete. The prerequisite adds important context. It lacks information about return values or error handling, but the low complexity keeps the gap small.

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 100%, and the schema already describes each parameter (app_id, file_id, content_base64). The description adds a small contextual note about file_id needing to exist, but does not expand on format or encoding requirements beyond the schema.

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 uses a specific verb ('Upload') and resource ('binary file content'), clearly distinguishing from siblings like create_file (metadata creation) and download_file (retrieval). The second sentence clarifies the dependency on create_file, reinforcing its role.

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?

States a clear prerequisite ('file metadata must be created first using create_file'), giving users a direct pointer to when to use this tool versus create_file. It does not explicitly mention alternatives like update_file or download_file, but the dependency is enough for basic usage.

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