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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not specify what the input 'q' should be (URL, path, base64), whether it fetches remote images, error behavior, or limitations. It only lists output fields, which is insufficient for a tool that likely requires an image reference.

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 extremely short, which is concise, but it's under-specification rather than conciseness. It front-loads the output fields, but omits essential operational details, so the brevity is not 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?

Given the tool has a single undocumented parameter, no annotations, and a large family of similar image tools, the description is severely incomplete. It fails to explain the input format, how the tool differs from siblings, or any behavioral constraints. The output schema exists but is not shown; the description must compensate but doesn't.

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 one parameter 'q' with no description and 0% coverage. The description does not explain what 'q' represents at all, so the agent has no way to construct a valid input. This is a critical gap.

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 states a clear resource (image metadata) and lists specific output fields (dimensions, format, mode, size, megapixels), which distinguishes it from purely tautological names. However, it does not explicitly differentiate from the many sibling image tools like imageexif or imagexmp, which also return metadata, so it's not a full 5.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't state that it handles basic metadata or that imageexif is for EXIF data. The description gives no context about input format, prerequisites, or exclusions, so an agent cannot decide between this and siblings.

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