Elenchus MCP Server

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 states this is a 'Set' operation, implying a mutation, but doesn't disclose behavioral traits like whether it requires specific permissions, if changes are reversible, potential side effects on other operations, or any rate limits. This leaves significant gaps for a mutation tool.

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 highly concise and front-loaded, consisting of two sentences that directly convey the tool's purpose and usage guidance without any wasted words. Every sentence earns its place by adding clear value.

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 moderate complexity (a single parameter mutation), no annotations, and no output schema, the description is somewhat complete but lacks depth. It covers the basic 'what' and 'how' but misses behavioral details (e.g., effects, reversibility) and output expectations, which are important for a mutation tool in this context.

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 100% description coverage, with the 'mode' parameter fully documented in the schema (including enum values and descriptions). The description adds minimal value by echoing the 'compact' and 'minimal' modes but doesn't provide additional semantics beyond what's in the schema, such as performance implications or default behaviors.

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's purpose with a specific verb ('Set') and resource ('response compression mode'), and mentions the goal ('token optimization'). However, it doesn't explicitly differentiate this from sibling tools like 'elenchus_configure_optimization' or 'elenchus_estimate_savings', which might have overlapping optimization domains.

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 on when to use each mode ('compact' for moderate savings, 'minimal' for aggressive savings), which helps guide selection. However, it doesn't specify when to use this tool versus alternatives (e.g., other configuration tools) or mention any prerequisites or exclusions, such as whether it requires an active session.

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