Upload a reference image

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

Annotations are minimal (all false), so the description carries most of the burden. It reveals it is a write operation and stores under a specific path, but lacks details on permissions, idempotency, or behavior on overwrite. No contradictions with annotations.

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?

Two sentences, front-loaded with the core action and location, then usage guidance. No redundant words or information. Very efficient.

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?

No output schema is provided, and the description does not mention return value, success/failure signals, or preconditions (e.g., project existence). With 4 parameters and some undocumented, the description is incomplete for a mutation tool.

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 50%, meaning two parameters lack descriptions. The tool description adds overall context (base64, utf8, path) but does not elaborate on each parameter individually (e.g., project, encoding). It fails to compensate for missing schema descriptions.

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 verb ('Save'), the resource ('reference/source image'), and the purpose ('to use as input for media generation'). It distinguishes from the gallery ('kept separate from the gallery') and explains usage in prompts. This fully differentiates from sibling tools like save_media.

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 (before generation) and mentions keeping separate, but does not explicitly state when not to use or provide alternatives. Siblings like save_media exist but are not compared. Usage context is clear but no exclusions are given.

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