Elenchus MCP Server

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the action is destructive ('Clear all cached verification results') and requires user confirmation ('Requires confirm: true'), which are critical for safe operation. It does not cover other aspects like rate limits or error handling, but the core behavior is well-described.

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 front-loaded with the core purpose in the first sentence and includes a crucial prerequisite in the second. Every sentence earns its place with no wasted words, making it highly efficient and well-structured.

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 (destructive operation with one parameter) and lack of annotations and output schema, the description is reasonably complete. It covers the purpose, prerequisite, and behavioral impact, though it could benefit from details on what happens after clearing (e.g., performance implications) or error cases.

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 already documents the 'confirm' parameter. The description adds minimal value by mentioning 'Requires confirm: true', which reinforces the requirement but does not provide additional meaning beyond what the schema specifies.

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 explicitly states the action ('Clear') and the target resource ('all cached verification results'), making the purpose specific and clear. It distinguishes from sibling tools like 'elenchus_get_cache_stats' by focusing on deletion rather than retrieval.

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 clear context by specifying 'Requires confirm: true', indicating a prerequisite for use. However, it does not explicitly state when to use this tool versus alternatives (e.g., no comparison to other cache-related tools) or when not to use it.

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