create_kb_image

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

Annotations already declare readOnly=false, destructive=false, openWorld=true and idempotent=false, so the safety profile is covered. The description adds workflow context (a backup step after visual inspection) but says nothing about batch limits, duplicate handling, quota consumption, or what happens on repeated calls despite idempotentHint=false.

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 tight sentences with the purpose and the parenthetical option front-loaded before the workflow caveat. No filler sentences; the second clause rambles slightly but earns its place as a misuse warning.

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 non-idempotent write tool with 5 params, 0% schema coverage and no output schema, the description is far too thin — it omits how images are addressed, what targetDocName does to existing docs, and what a successful response contains.

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 0% for 5 parameters, so the description must carry parameter meaning and does not. It only nods to autoCaption; it never explains images (data vs sourceUrl, mimeType), targetDocName (append vs overwrite), tags, or agentId, leaving the agent to guess at required-parameter semantics.

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 gives a specific verb and resource ("Upload images into the agent KB") and flags an optional mode (autoCaption), so an agent can tell this creates image entries in the knowledge base. It does not explicitly distinguish itself from siblings like import_file_to_kb or create_kb_doc, which are the closest overlapping tools.

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 gives real sequencing guidance — call read_image and label the photos in the system prompt first — and adds an exclusion ("not a substitute for looking at them"), which prevents misuse. It still leaves open when to pick this over import_file_to_kb or bulk_create_kb_docs.

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