read_image_metadata

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

No annotations are provided, so the description must carry full behavioral disclosure. It discloses that the tool reads embedded JSON metadata and returns an object with specific fields, but does not mention error behavior for missing files or files not generated by this server. This is adequate for a simple read operation but leaves some edge cases unaddressed.

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 two sentences, front-loaded with the action, and contains no fluff. Every sentence adds value: the first states what it does and the scope, the second states what is returned.

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 one-parameter read tool, the description is largely complete. It names the return fields (dimensions, color, shape, description) though there is no output schema, and it clarifies the file type and provenance. It could be more exhaustive about return structure, but given the simplicity, this is slightly above adequate.

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?

With 100% schema description coverage, the parameter 'filepath' is already fully documented in the schema. The tool description adds the context that the file must be a PNG generated by this server, but the schema provides the essential meaning. This is the baseline 3.

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 'Reads' and the specific resource 'embedded JSON metadata from a PNG file', immediately distinguishing this tool from its generation-focused siblings. It also scopes the tool to files generated by this MCP server, which is precise.

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 the tool is for reading metadata from already-generated PNG files, contrasting with sibling tools that generate assets. It gives clear context but does not explicitly state when not to use it or name alternatives, 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.