Metro Logs MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Clear' implies a destructive operation, but the description doesn't specify whether this is permanent, reversible, requires special permissions, or affects system performance. No rate limits, side effects, or response format information is included.

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 at just 3 words ('Clear the log buffer'), front-loaded with the core action, and contains zero wasted words. Every word earns its place in conveying the essential purpose.

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 destructive operation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'clear' means operationally, what happens to the cleared logs, whether the action is reversible, or what confirmation/response the tool provides. The context signals show this is a mutation tool in a system with many read-oriented siblings, making behavioral transparency particularly important.

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 0 parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters, and it doesn't attempt to add parameter information beyond what's already covered by the empty schema.

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 'Clear the log buffer' clearly states the action (clear) and target resource (log buffer), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_logs' or 'search_logs' beyond the obvious action difference.

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 about when to use this tool versus alternatives like 'get_logs' or 'search_logs'. The description doesn't mention prerequisites, timing considerations, or any context for when clearing logs is appropriate versus reading them.

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