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 mentions the transformation action and output behavior (saving to a file), but doesn't address important behavioral aspects like whether the operation is destructive to the original file, what permissions are required, error conditions, or performance characteristics. The description provides basic operational context but lacks comprehensive behavioral transparency.

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 efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence earns its place by providing essential information without redundancy. The formatting with 'Args:' section organizes parameter information effectively while maintaining brevity.

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 (image transformation with 3 parameters), no annotations, but with an output schema present, the description provides adequate context. It explains the core operation and all parameters, though it could benefit from more behavioral context about file handling, error conditions, or performance. The existence of an output schema means the description doesn't need to explain return values, which helps its 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?

With 0% schema description coverage, the description compensates well by explaining all three parameters: 'path' as the absolute path to the image file, 'direction' with its allowed values ('horizontal' or 'vertical'), and 'output_path' with its default behavior. The description adds meaningful semantics beyond what the bare schema provides, though it doesn't specify file format constraints or path validation rules.

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 ('flip/mirror') and resource ('an image'), specifying the transformation type (horizontal or vertical). It distinguishes from siblings like rotate_image, resize_image, and crop_image by focusing specifically on mirroring operations rather than other image manipulations.

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 provides no guidance on when to use this tool versus alternatives. While it's clear this is for flipping images, there's no mention of when flipping is appropriate versus rotating, cropping, or applying filters. No prerequisites, exclusions, or comparison to sibling tools are provided.

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