view_image

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool reads a file and returns it, and which formats are supported. However, it does not describe the return format (e.g., base64, binary), error handling for missing/invalid files, or any safety constraints. The basic behavior is disclosed, but important details are omitted.

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 one sentence plus a short format list. It is front-loaded with the core action and purpose, with no superfluous words. Every sentence earns its place.

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 operation with one parameter and no annotations, the description covers the primary use case. However, with no output schema provided, it does not explain the exact return representation or how the image will be delivered for vision analysis. This is a significant gap for an agent deciding whether the tool will meet its needs.

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?

The input schema already fully documents the single 'path' parameter with the description 'Absolute path to the image file.' The tool description adds no additional parameter-level meaning beyond the schema, so the baseline of 3 applies. Supported formats are a tool-level trait, not 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 clearly states the tool's function: 'Read an image file and return it for AI vision analysis.' It uses a specific verb ('read') and resource ('image file'), and distinguishes itself from siblings like screenshot (captures new images) and delete_image (removes files). The list of supported formats adds specificity.

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 context is clear: use this tool when you need to analyze an existing image file with AI vision. It does not explicitly name alternatives or exclusions, but the purpose is distinct enough from sibling tools (screenshot, screenshot_region) that an agent would not confuse them. The description implies it is for reading pre-existing files, not capturing new ones.

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