image_metadata

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

The description discloses 'no cloud call', which is useful behavioral context. However, it also claims 'requires local file path', which is factually false given the schema allows URLs and base64. Since no annotations exist, the description's inaccuracy is a significant transparency failure.

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 short sentence, which is concise, but it packs a false claim about local paths. While the length is appropriate, the inaccuracy prevents it from being fully effective.

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?

It lists metadata types and notes offline behavior, but fails to reconcile the local-path statement with the schema's broader input support. It also does not explain when to use this tool versus sibling tools like analyze_image, and since there is no output schema, return details are missing.

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 schema has 100% coverage for the 'image' parameter, so baseline is 3. But the description actively adds incorrect information by stating 'local file path required', directly contradicting the schema. This negative contribution reduces the score.

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 reads image metadata (dimensions, format, color mode, EXIF/GPS) with a specific verb and resource. However, the qualifier 'local' conflicts with the schema's support for URL/base64, slightly muddying the scope.

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?

It mentions 'requires local file path' and 'does not call cloud', implying a context of offline local use, but gives no explicit alternatives or exclusions. The local-path requirement is contradicted by the schema, making the guidance misleading.

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