Analyze Image

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it uses a vision AI model and details supported input formats (base64 data URL, HTTP link, local file path). It doesn't disclose failure modes or rate limits, but given the annotation coverage, this is a meaningful addition.

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 three succinct sentences: purpose, when to call, and input formats. It is front-loaded with the primary function and every sentence contributes distinct value without redundancy or fluff.

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 read-only analysis tool with two well-documented parameters, the description covers the purpose, usage, and input formats thoroughly. The 'see' metaphor implies a textual output, and the examples clarify what to expect. It omits explicit return format or size limits, but those are not critical for an AI agent to invoke the tool 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?

Schema description coverage is 100%, with both 'image' and 'prompt' clearly documented including formats, requirements, and examples. The description adds no new parameter-level information beyond what the schema provides, so it does not exceed the baseline for high coverage.

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 uses a specific verb 'Analyze' with the resource 'image', immediately clarifying the tool's function. It goes further by explaining the purpose ('giving a non-vision main model the ability to see') and listing concrete use cases (describe, OCR, identify UI elements, read charts). There are no siblings, so differentiation is not required.

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 explicitly states 'Call this when the user sends an image, or when you need to understand an image', providing clear trigger conditions. It also enumerates example analysis types, which helps the agent decide when to use the tool. No alternatives exist, but the guidance is strong and actionable.

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