media-mcp

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It doesn't disclose whether this is a destructive operation (overwrites files?), what permissions are needed, potential side effects, or error handling. The mention of default values and supported formats adds some context but falls short of 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 a bullet-point-like parameter explanation. Every sentence earns its place by providing essential information without redundancy. The formatting with 'Args:' section enhances readability 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 complexity (video conversion with multiple parameters), no annotations, but with output schema present, the description is reasonably complete. It thoroughly documents parameters and conversion options but could better address behavioral aspects like file safety, performance characteristics, or common use cases relative to sibling tools.

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 fully compensates by explaining all 5 parameters in detail. It clarifies 'path' as absolute path, 'format' with examples and supported list, 'output_path' default behavior, 'resolution' format examples, and 'crf' meaning and range. This adds substantial value beyond the bare schema.

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 with specific verbs ('convert') and resources ('video'), distinguishing it from siblings like 'convert_image' or 'extract_frames'. It explicitly mentions both format and resolution conversion, making the scope 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 through the stated purpose but provides no explicit guidance on when to use this tool versus alternatives like 'extract_frames' or 'create_thumbnail'. It doesn't mention prerequisites, error conditions, or comparative scenarios with sibling tools.

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