extract_image_metadata

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

The description mentions a cost ($0.002 USDC via x402), which is a behavioral trait not in annotations (none provided). However, it does not clarify if payment is mandatory, what happens without paymentHeader, or any side effects. No annotations exist, so description carries burden but adds limited transparency beyond cost.

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?

Two sentences, front-loaded with purpose ('Extract metadata from image (EXIF, GPS, IPTC, XMP).'), then pricing. No redundancy. Could be slightly more informative about payment flow, but overall efficient and well-structured.

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 nested input schema (includeOptions), optional payment parameters, and no output schema. The description does not explain the return format, the meaning of includeOptions, or how payment works (x402). Given the complexity and missing output schema, the description is incomplete.

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 75% (all parameters have descriptions, nested options have defaults). The tool description adds no additional parameter-level information beyond what the schema provides. At high coverage, baseline of 3 is appropriate.

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 verb 'Extract' and resource 'metadata from image', and lists specific metadata types (EXIF, GPS, IPTC, XMP). It distinguishes from siblings like detect_image_manipulation (manipulation detection) and extract_batch_metadata (batch operation) by implying single image focus.

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 explicit guidance on when to use vs alternatives like batch extraction or pricing tool. The description implies single image use but does not address when to choose this over extract_batch_metadata or detect_image_manipulation. The pricing info is a usage hint but not a guideline.

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