media-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool applies filters and saves output, but doesn't mention whether the original file is modified, what permissions are needed, error conditions, or performance characteristics. The default output path behavior is helpful but insufficient for a mutation tool with zero annotation coverage.

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, bulleted filter list, and parameter explanations. Every sentence adds value: the first states the core function, the second enumerates options, and the third explains parameters with useful defaults. No wasted words.

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 an output schema (which presumably describes the return value), the description doesn't need to explain return values. However, for a mutation tool with 3 parameters and no annotations, it should provide more behavioral context about side effects, error handling, and constraints. The parameter explanations are good but the overall context is incomplete.

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 absolute file path, 'filter_name' with enumerated options, and 'output_path' with default behavior. It adds meaningful context beyond the bare schema, though it doesn't specify file format constraints or filter-specific details.

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 tool's purpose: 'Apply a filter to an image' with a specific verb ('apply') and resource ('image'). It distinguishes from siblings by focusing on filtering rather than compression, conversion, cropping, etc. However, it doesn't explicitly differentiate from all siblings (e.g., 'emboss' might overlap with 'edge_enhance' conceptually).

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 like 'convert_image' or 'create_thumbnail'. It lists available filters but doesn't explain which filters are appropriate for what scenarios or when to choose this over other image manipulation tools. No exclusions or prerequisites are mentioned.

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