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

The description thoroughly discloses that non-strip uploads replace and delete previous images from storage and DB, while strip uploads accumulate. This directly contradicts the annotation destructiveHint=false, which signals a non-destructive operation. Because the description contradicts an annotation, the score is capped at 1 per the rubric.

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 appropriately detailed for a complex tool, with bolded purpose categories and bullets. Every sentence earns its place, explaining behavior, lifecycle, scope, and endpoint mapping without excessive filler. The only trivial redundancy is the title-like first line 'Upload an image.'

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?

Despite no output schema, the description covers endpoint mapping, required multipart fields, purpose-specific behavior, deletion side effects, scope (images:manage), billing/rate limits, and the returned id for strip usage. An agent has enough context to invoke the tool correctly and interpret the result.

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%, so the schema already documents purpose, file_base64, filename, and x_app_id. The description mostly restates the schema's purpose semantics (strip accumulates, others replace) and adds only minor reinforcement about multipart encoding. This meets the baseline but does not materially expand on 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 names the resource (image), its use cases (pass templates or per-pass strip overrides), and maps to a concrete endpoint/operationId (POST /manage-images, uploadImage). It clearly differentiates from sibling upload* tools like uploadCertificate and uploadGoogleCredentials by specifying images and their purposes.

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 states when to use the tool: for pass template assets or per-pass strip overrides, and gives detailed purpose-by-purpose behavior. It does not explicitly list exclusions such as 'do not use for certificates or credentials,' but the image scope and operation mapping make the boundary clear enough.

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