Upload an image

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

No annotations are provided, so the description carries the burden. It states the action and the membership requirement, but it does not disclose whether the upload is a write operation that persists data, whether it is idempotent, or any side effects beyond returning a URL. Some behavioral details are missing.

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 compact—two sentences—and includes all essential details without redundancy. It is well-structured with clear conditions and constraints, making it efficient to parse.

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 tool with 4 parameters and no output schema, the description covers the core usage, input options, and constraints. It does not mention error scenarios or URL permanence, but these are not critical for selecting and invoking the tool. Overall, it is complete enough for an agent to use correctly.

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?

The schema already describes each parameter, but the description adds critical context: max file size, allowed formats, that base64 requires a filename, that file_path overrides base64, and the exact banner dimensions. This significantly enriches the parameter meanings beyond the schema.

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 action (upload image), the resource (image), and the purpose (to get a hosted HTTPS URL for banner or article usage). It also specifies supported formats and size limit, leaving no ambiguity about the tool's function.

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?

It explicitly instructs to provide either a local file path or base64 content with a filename, and clarifies that banner type requires matching dimensions. The paid membership requirement is also disclosed, giving the agent clear conditions for successful use.

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