upload_file

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

Annotations provide readOnlyHint=false, idempotentHint=false, destructiveHint=false. Description adds that file_data must be base64-encoded (not URL or raw bytes) and explains folder_id usage. No contradictions.

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?

Well-structured: summary, usage advice, Args list, Returns list. Each sentence adds value. No fluff.

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?

Covers all parameters, provides return value details (id, full_size_url, etc.), and gives usage context for campaign/template content. Output schema exists but description still explains return fields. Sibling tools are many but tool is well-differentiated.

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 0%, but description explains name (extension, shown in File Manager), file_data (base64-encoded), and folder_id (optional, from list_file_folders). Missing account parameter (not described) but covers 3 of 4 well.

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?

Clearly states the verb 'upload', resource 'image or file', and context 'File Manager (base64-encoded)'. Distinguishes itself from siblings like list_files, delete_file, and list_file_folders by mentioning their use cases.

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?

Explicitly states when to use: for programmatic image hosting in campaigns/templates. Provides alternatives: use list_file_folders to target a folder, list_files to browse, delete_file to remove. Gives clear context.

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