EpicMe 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 but offers minimal information. It states the tool 'returns' something, implying a read-only operation, but doesn't specify whether it's a simple fetch, has side effects, requires authentication, involves rate limits, or what format the return value takes. The description lacks details on what 'MCP_TINY_IMAGE' represents or how it behaves, leaving significant gaps in understanding.

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 extremely concise with a single, straightforward sentence: 'Returns the MCP_TINY_IMAGE'. It's front-loaded and wastes no words, making it easy to parse quickly. Every word earns its place by conveying the core action, though it lacks depth.

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 simplicity (0 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'MCP_TINY_IMAGE' is, what 'returns' entails (e.g., data format, potential errors), or how it fits into broader workflows. While minimal context might suffice for a trivial tool, this leaves too many unanswered questions about usage and output.

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?

The tool has zero parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics since there are none to explain. This meets the baseline of 4 for tools with no parameters, as there's no gap to compensate for.

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 'Returns the MCP_TINY_IMAGE' is a tautology that essentially restates the tool name 'getTinyImage' with slightly different wording. It doesn't specify what the MCP_TINY_IMAGE actually is (e.g., an image resource, metadata, URL) or what 'returns' means in practical terms. While it indicates a retrieval action, the purpose remains vague and indistinguishable from other retrieval tools like 'getResourceLinks' or 'getResourceReference'.

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 any specific context, prerequisites, or exclusions, nor does it differentiate it from sibling tools like 'getResourceLinks' or 'getResourceReference' that might also retrieve resources. There's no indication of when this tool is appropriate or what problems it solves.

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