clear_logs

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

The description adds meaningful behavioral context: it specifies that all logs are cleared (scope) and that the action cannot be undone (irreversibility). These go beyond the destructiveHint and idempotentHint annotations. However, it does not mention any prerequisites or side effects on other device state.

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 consists of two concise sentences, front-loaded with the core purpose and followed by a succinct warning. No wasted words.

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?

The tool is simple with one optional parameter, and annotations provide destructive/idempotent hints. The description covers the core action and irreversibility, but fails to explain the 'device' parameter semantics or what happens when it is null. With an output schema present, return values need no explanation, so it is adequate but not complete.

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 one parameter 'device' with 0% description coverage, and the description does not explain its meaning, valid values, or behavior when null. The only mention is the phrase 'from the MikroTik device', which does not clarify whether the parameter is required or how it is used.

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 action (clears), the target (all logs), and the scope (from the MikroTik device). It is distinguishable from sibling log tools like get_logs, search_logs, export_logs, which do not mention clearing.

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 vs alternatives. It does not mention alternatives like export_logs for preserving logs, or get_logs for reading. No exclusions or prerequisites are given. This is purely a purpose statement.

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