get_image_info

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

With no annotations, the description carries the full burden of disclosure. 'Get' implies a read-only operation and the parameter description adds that it accepts a path or URL. However, it does not disclose behavior such as error handling or whether the metadata is fetched locally or remotely, making it minimally adequate but not detailed.

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 a single concise sentence that directly states the tool's function. Every word contributes value, and it is appropriately front-loaded with no filler or redundancy.

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 tool with one parameter and no output schema, the description is insufficient. It does not indicate what specific metadata will be returned (e.g., dimensions, format, size), leaving the agent to guess the return structure. Given the absence of an output schema, the description should compensate by listing example metadata fields.

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% with a single parameter clearly described as 'Image path or URL'. The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate. It does not elaborate on formats or examples.

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 with a specific verb ('Get') and resource ('metadata and information about an image'). It distinguishes itself from sibling manipulation tools since it is read-only, though it could be more specific about what metadata is included.

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 guidance on when to use this tool versus alternatives like optimize_image or add_watermark. It is implicitly understood that this is for inspection before editing, but the description does not explicitly state this or provide any usage context.

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