tool_exif_viewer

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

With no annotations, the description carries the full burden for behavioral disclosure. It does not state that the tool is read-only, that it only reads metadata without modifying the file, or any constraints like file size limits or supported formats. The output is only labeled 'EXIF Data', with no detail on structure. This is minimal and insufficient for safe invocation.

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 short and uses a clear list format for parameters and outputs. Every line contributes to specifying how to call the tool. It is not overly verbose, though the title and parameter list could be more integrated. The structure is easy to parse programmatically.

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 tool has no output schema and no annotations, yet the description only says the output is 'exif (json): EXIF Data' without describing the JSON structure or what fields will be present. The purpose of the 'category' parameter is not explained, and there is no mention that the file must be an image. This is a notable gap for a tool with a nested input object.

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?

Although schema coverage is 100%, the description actively misrepresents the file parameter as 'bytes', while the schema defines it as a nested object with base64, filename, and mimeType. This contradiction can mislead an agent into passing raw bytes instead of the required base64 object. The category parameter description adds no meaning beyond the schema, and the exif output is not a true input parameter.

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 'EXIF Viewer' with '[image]' prefix clearly indicates the tool views EXIF metadata from an image file. It is a noun-phrase title rather than an explicit verb phrase, but the purpose is unambiguous given the parameter/output listing. No sibling tool is an EXIF viewer, so differentiation isn't needed.

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?

No guidance is provided for when to use this tool or what alternatives exist. The description does not mention prerequisites, such as the file needing to be an image, nor does it explain the role of 'category'. There is no 'when to use' or 'when not to use' information.

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