upload_image_to_drive

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

No annotations are provided, so the description carries full burden. It mentions the tool 'uploads' (implying a write operation) and returns file ID and web link, but lacks critical behavioral details: required permissions, rate limits, file size constraints, error handling, or whether it overwrites existing files. For a mutation tool with zero annotation coverage, this is insufficient.

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 concise and well-structured: three sentences that cover purpose, input, and output without redundancy. However, the second sentence could be more front-loaded by merging with the first, and it lacks critical behavioral details that would justify additional length.

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 the tool's complexity (mutation with 3 parameters), no annotations, and an output schema (which covers return values), the description is incomplete. It misses essential context: authentication requirements, error cases (e.g., invalid MIME types), sibling tool differentiation, and usage prerequisites. The output schema helps, but the description should compensate for missing annotations.

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 67% (2 of 3 parameters have descriptions). The description adds minimal value beyond the schema: it clarifies that 'image' is 'base64-encoded data with MIME type' (schema already references ImageContent with mimeType) and mentions returns (covered by output schema). It doesn't explain 'parent_folder_id' behavior (e.g., default location if null) or 'name' constraints (e.g., uniqueness). Baseline 3 is appropriate given moderate schema coverage.

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 clearly states the tool's purpose: 'Upload an image to Google Drive' specifies the verb (upload) and resource (image to Google Drive). However, it doesn't explicitly differentiate from sibling tools like 'upload_file_to_drive' or 'upload_image_to_drive_from_resource', which handle similar functions with different input sources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'upload_file_to_drive' (for general files) or 'upload_image_to_drive_from_resource' (for images from resources), leaving the agent to infer usage based on parameter names alone.

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