upload_image

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

Annotations are absent, so the description bears the full burden. It mentions offloading to a third-party CDN and returning a public URL, but for a mutation tool with no annotations it fails to disclose return format, file size limits, link expiration (e.g., ImgBB's 30-day retention on free tier), or authentication requirements. The 'high-speed' language is promotional filler that doesn't add behavioral substance.

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?

A single, scannable sentence that front-loads the action and outcome. Every word earns its place; 'high-speed' is mildly promotional but harmless. Zero 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?

For a simple 2-parameter tool with no nested objects, enums, or output schema, the description is nearly adequate end-to-end. However, given no annotations, a bit more context (e.g., rate limits, typical latency, or that the CDN URL may be temporary) would elevate this to genuinely helpful rather than merely functionally sufficient.

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% for both parameters, so per guidelines the baseline is 3. The description adds no parameter-specific context beyond the schema — e.g., it doesn't clarify acceptable image formats, size limits, URL encoding rules, or what 'public' implies about accessibility. Baseline of 3 holds because the schema already documents the parameters adequately.

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 uses a specific verb ('Upload'), resource ('any image to ImgBB CDN'), and clear outcome ('get back a public high-speed URL'). It clearly distinguishes this from all siblings (get_site_stats, create_post, etc.), none of which handle image uploads.

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 implies when to use this tool (whenever an image upload is needed) and differentiates from siblings by being the only upload-capable tool. However, it provides no explicit guidance on when NOT to use it, no prerequisites (e.g., auth), and no alternative tool names, relying on obviousness.

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