media-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it removes metadata for privacy, creates a clean copy (implying non-destructive operation), and specifies default output naming. However, it does not mention potential side effects, file format support, or error conditions, leaving some gaps.

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 front-loaded with the core purpose, followed by outcome and parameter details in a structured format. Every sentence adds value without redundancy, and the Args section is efficiently formatted, making it easy to parse quickly.

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's moderate complexity (2 parameters, no annotations, but with an output schema), the description is largely complete. It covers purpose, behavior, and parameters well. The presence of an output schema means return values need not be explained, but it could benefit from mentioning supported image formats or error handling for full completeness.

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 0%, so the description must compensate fully. It clearly explains both parameters: 'path' as the absolute path to the image file, and 'output_path' with its default behavior ('Defaults to <name>_clean.<ext>'). This adds essential meaning beyond the bare schema, making parameter usage clear.

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 specific action ('Remove all EXIF and metadata') and target resource ('from an image'), distinguishing it from sibling tools like compress_image or resize_image. It explains the privacy purpose and outcome ('Creates a clean copy of the image with no embedded metadata'), making the tool's function unambiguous.

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 usage for privacy purposes when metadata removal is needed, but does not explicitly state when to use this tool versus alternatives (e.g., get_image_info for viewing metadata) or any prerequisites. It provides basic context but lacks explicit guidance on tool selection among siblings.

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