media-mcp

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

With no annotations provided, the description carries full burden. It explains the core behavior (resizing to fit square, preserving aspect ratio) and mentions default behavior for output_path, but doesn't cover error handling, file format support, permissions needed, or what happens if output_path exists. Some behavioral context is provided but not comprehensive.

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 adds value with no redundant information. The Args section is well-organized and directly supports tool invocation.

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 handles return values), no annotations, and good parameter coverage in the description, the description is reasonably complete. It explains the transformation behavior and parameters adequately, though could benefit from more behavioral context about edge cases or limitations.

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 (absolute path to image), size (thumbnail size in pixels with default 256), and output_path (where to save with default naming convention). It adds meaningful context beyond the bare schema types.

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 creates a square thumbnail from an image, specifying it resizes to fit within a square while preserving aspect ratio. This distinguishes it from sibling tools like resize_image (general resizing) and crop_image (cropping rather than fitting).

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 creating thumbnails with square aspect ratios, but doesn't explicitly state when to use this versus alternatives like resize_image or crop_image for similar tasks. No guidance on prerequisites or exclusions is provided.

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