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

With no annotations provided, the description carries the full burden and does a solid job: it discloses that the operation is free, that dimensions may be omitted if the header cannot be read, that C2PA manifests are reported but not validated, and that the tool fetches from URL or base64. It does not cover auth/privacy caveats, but for this tool the disclosed limitations are meaningful and relevant.

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 opens with a clear one-line purpose and uses a structured responses section for practical detail. It is moderately sized and front-loaded, though the example response mentions only two of the many documented output fields, which is slightly misleading and prevents a perfect score.

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 one-parameter tool with no output schema, the description is fairly complete: it names the main metadata fields, the cost output, the C2PA behavior, and a key failure mode (unreadable header). A minor gap is that it does not enumerate which vision models are considered, but this is not essential for invoking the tool.

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 input schema already documents the single 'source' parameter with good coverage, including public URL, base64, and data URI formats. The description adds little beyond repeating 'URL or base64' and does not enrich the schema's meaning, so the baseline 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 uses a specific verb ('Fetch... and return') with a clear resource ('image metadata') and enumerates concrete outputs: size, pixel dimensions, source format, vision model token costs, and C2PA presence. This clearly distinguishes analyze_image from sibling transformation tools like compress_image, resize_image, and crop_image.

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?

The description implies its use case by listing what it returns—especially the free token cost estimate for vision models—and the 'Always free' note provides practical selection context. However, it does not explicitly state when not to use it or name alternatives such as estimate_cost, so it falls short of a 5.

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