Add an image the chatbot can show

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

Discloses only that it adds an image; no mention of persistence, overwrite behavior, URL validation, or side effects. Annotations only provide false hints, so the description carries the burden and doesn't meet it.

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, but the second sentence is meta-commentary about the description parameter and overlaps with the schema; it could be tightened without losing core meaning.

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 create-like operation with no output schema, it states the basic action and key parameter nuance, but omits return behavior, errors, and usage context.

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 covers all three parameters with descriptions; the tool description adds extra semantic context for the description parameter ('what the AI reads to decide when the image answers the question'), going beyond the schema's basic text.

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?

States 'Add an image the chatbot may show' with a clear verb and resource, distinguishing it from list_images/delete_image. The second sentence is meta-instruction about the description parameter and slightly muddies the tool-level purpose.

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?

No guidance on when to use this tool versus add_knowledge_text/add_product/add_webhook, no prerequisites, and no mention of how to decide among image-related operations.

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