upload_file

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

Annotations indicate non-destructive, non-idempotent, read-write behavior. The description adds value by clarifying that by default it appends (non-destructive) and that setting replace=true overwrites. It also specifies the input format (base64). No contradictions with annotations.

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, front-loaded with the core action and format, then a critical usage detail. No redundancy or wasted words.

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?

With 6 parameters, 5 required, and no output schema, the description adequately covers the essential behavior: file upload via base64, attach to column, append/replace semantics. It could mention file size limits or supported formats, but the description is functional for a file upload tool.

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?

Input schema describes all 6 parameters with 100% coverage. The description adds minimal extra meaning beyond the schema, primarily clarifying the append vs replace behavior and the base64 encoding requirement. Baseline 3 is appropriate.

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 'Upload a file or image to a row' and specifies the input format (base64). It distinguishes from siblings like 'download_file' by focusing on upload, though it could explicitly differentiate from 'update_rows' which also modifies data.

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?

Provides clear context: accepts base64 data, attaches to specified column, and explains default behavior (append vs replace). However, it does not explicitly mention when not to use this tool (e.g., for large files, alternative upload methods) or contrast with related tools like 'update_rows'.

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