analyze_image

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses the two operational modes and their behavior (full visual understanding vs. OCR text extraction), which is sufficient for a read-only image analysis tool.

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 concise and well-structured: trigger conditions, usage caveat about native vision, and mode selection guidance are all front-loaded. No sentence is wasted, and the note about native vision is essential for correct agent decision-making.

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?

The description covers the core context: what the tool does, when to invoke it, how to choose modes, and the required parameter. An output schema exists, so the return format does not need explanation. The tool is simple with only two parameters, and the description is complete for correct invocation.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining when to use mode=ocr versus mode=full, which goes beyond the schema's brief mode description. The path_or_url parameter is already well-covered by 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 clearly states the tool's purpose: when the user provides an image, screenshot, chart, or photo, call the tool to obtain a visual content description. It uses a specific verb and resource, and the note about native vision distinguishes its intended role from the model's own capabilities.

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 defines when to use the tool (when the model cannot directly view images) and when not to use it (if the model has native vision). It also provides clear mode selection guidance: use mode=full by default, and mode=ocr only for explicit text/table extraction.

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