Clear MCP Cache

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

The description indicates it clears an in-memory cache, which is non-destructive but does not disclose side effects or scope. Since no annotations exist, the description carries the burden, but it omits details like idempotency, impact on other cached data, or performance implications.

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, concise sentence that immediately conveys the action. Every word serves a purpose with no waste.

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?

For a simple, parameterless tool with no output schema, the description adequately explains the function. It could mention that it affects all users of the server, but overall it is sufficient.

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 input schema has zero parameters, so there is nothing for the description to add beyond what the schema provides. A baseline of 4 is appropriate since no parameter information is needed.

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 clears the MCP server's in-memory Hypixel and Mojang response cache. The verb 'Clear' and specific resource are well-defined, and none of the sibling tools have similar cache-clearing functionality.

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?

No guidance is provided on when to use this tool versus alternatives, or under what circumstances cache clearing is appropriate. The description lacks context such as 'use after data updates' or 'to force refresh'.

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