conversations_initiate_file_upload

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds no behavioral context beyond that: it doesn't explain what side effects occur (e.g., creating a resumable upload URL), whether authentication is needed, or what happens if the upload isn't completed. Since the annotations cover safety, the description adds minimal value here.

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?

The description is only six words, which is concise and front-loaded, but it's too sparse to provide meaningful context. It reads as a fragment rather than a structured explanation. It earns a 3 because it's not verbose, but it lacks the substance that would make it genuinely helpful.

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?

This tool is part of a multi-step upload process (initiate then complete), but the description doesn't mention the follow-up step or what the response contains (e.g., an upload URL or ID). With six parameters and no output schema, the description should explain the flow and any dependencies. It falls short, leaving the agent without critical information to use the tool correctly.

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 description coverage is 100%, so the schema fully documents all six parameters (channel, fileSize, filename, locationId, contentType, conversationId). The description adds no parameter-specific details. Baseline of 3 is appropriate when the schema does the heavy lifting.

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 verb ('Initiate') and resource ('file upload to GCS'), making the core action clear. However, it does not explicitly differentiate from the sibling tool conversations_complete_file_upload, which is the logical follow-up step. The name itself hints at a two-step process, but the description doesn't clarify the relationship.

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 is provided on when to use this tool vs. alternatives like conversations_complete_file_upload or conversations_add_message_attachments. The description doesn't mention the prerequisite of having a conversation ID or the requirement to call a completion step after initiating. The agent is left to infer the workflow from the tool name alone.

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