foto_inspect_image

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

With no annotations, the description carries the full burden, and it does disclose one valuable trait: the file is processed locally and never uploaded, which implies a safe read-only, privacy-preserving operation. It omits error behavior for missing/unreadable files, what happens with unsupported formats, and whether metadata is ever written back, which matters for a tool with zero annotation coverage.

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?

A single sentence, front-loaded with the verb and the 'without uploading' guarantee, then the enumerated return contents. No filler and nothing that could be cut without losing information.

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 single-parameter read tool with no output schema, the description does the important work of enumerating what comes back (EXIF fields, dimensions, aspect ratio, GPS flag). Only the failure modes and format-rejection behavior are left unstated, which is a modest gap given the tool's low complexity.

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?

Only one parameter and schema coverage is 100%, with the schema itself documenting the absolute path and the accepted formats (JPEG, PNG, WebP, HEIC, TIFF). The description merely echoes 'local image file' and adds no format, path, or permission nuance beyond the schema, so baseline 3 applies.

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?

States a specific verb (inspect) and resource (local image file) plus the exact payload returned: EXIF camera/lens/ISO/shutter/aperture, dimensions, aspect ratio, GPS presence. The 'without uploading' qualifier further distinguishes it from the posting/sync siblings, which all involve remote operations.

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?

Usage is only implied: an agent can infer this is a pre-flight check before drafting or publishing, but the description never says when to prefer it over the other foto_* tools or states any exclusions. No alternative is named, so routing relies on inference from the sibling names.

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