inspect_image

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

The annotations already declare this as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavioral context by listing the measured outputs and explaining that include_thumbnail returns a small preview image, but it does not cover supported formats, error behavior, or how the file is accessed.

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 compact and front-loads the main purpose before listing measured properties and the optional thumbnail behavior. The dense list of measurements is efficient, though it could be organized more clearly into returned values versus parameter behavior.

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 two-parameter, read-only inspection tool with no output schema, the description does list the main returned measurements and the thumbnail option. It remains incomplete around path requirements and sibling differentiation, which matters because several other tools appear to operate on images or style analysis.

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%, so the description must compensate for both parameters. It explains include_thumbnail reasonably well, but it does not clarify the required path parameter, accepted file types, path format, or whether the path must point to a local image file.

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 identifies the resource and the kind of result: metadata and measured style of an image file, including specific measurements such as tone, white balance, saturation, grain, vignette, palette, and descriptors. It does not, however, differentiate this tool from nearby siblings like analyze_style, open_image, or render_preview.

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?

There is no explicit guidance on when to use inspect_image versus alternatives such as analyze_style, open_image, or render_preview. The description implies it is used to inspect image properties, but it gives no exclusions, prerequisites, or alternative routing.

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