EpicMe MCP

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

No annotations are provided, so the description carries the full burden. It mentions the tool compresses files and returns a data URI, but lacks details on behavioral traits such as error handling (e.g., invalid URIs), performance (e.g., size limits), or side effects (e.g., network requests for URIs). This is inadequate for a tool that processes external resources.

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 a single, well-structured sentence that efficiently conveys the tool's purpose, input, and output without unnecessary details. It is front-loaded with the core action and avoids redundancy, 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 complexity (processing multiple external files) and lack of annotations or output schema, the description is insufficient. It doesn't explain return values (e.g., structure of the data URI), error conditions, or limitations, leaving gaps for safe and effective tool invocation by an AI agent.

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 100%, so the schema fully documents the 'files' parameter as a mapping of file names to URLs. The description adds marginal value by specifying that URIs can be data URIs and clarifying the mapping purpose, but doesn't provide additional syntax or format details beyond what the schema already covers.

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 ('compresses'), the resource ('provided resource files'), and the output ('to a zip file, which it returns as a data URI resource link'). It distinguishes itself from sibling tools like 'getResourceLinks' or 'getTinyImage' by focusing on compression rather than retrieval or image processing.

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. It doesn't mention prerequisites (e.g., file availability), exclusions (e.g., unsupported file types), or compare it to sibling tools like 'add' or 'structuredContent' for handling multiple files. Usage is implied but not explicitly stated.

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