Banana Image MCP

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

With no annotations provided, the description carries the full burden. It discloses the WebP conversion side effect and CDN URL return, but omits mutation safety details (overwrite behavior, idempotency, whether local files are deleted), authentication requirements, or error conditions.

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?

Single sentence of 15 words with zero waste. Front-loaded with the core action, includes all key elements (source types, destination, transformation, output), and avoids filler words or redundant phrases.

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 3-parameter upload tool with no output schema, the description adequately covers the essential contract: input handling, processing side effects, and return value. Minor gaps remain regarding error handling, overwrite semantics, and authentication, but the core functionality is well-documented.

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%, establishing a baseline of 3. The description adds minimal parameter-specific context beyond the schema, though 'local or remote' reinforces the source parameter's dual-purpose nature. No additional syntax guidance or format examples are provided.

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 specific action (upload), resource type (image), destination (Qiniu CDN), transformation (convert to WebP), and return value (CDN URL). It effectively distinguishes from siblings generate_image and generate_blog_cover by emphasizing 'upload' versus generation.

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?

While the verb 'upload' implies usage for existing images versus generating new ones, the description lacks explicit when-to-use guidance or named alternatives. It does not clarify whether to use this versus the generate_* siblings when both might apply.

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