mikrotik_execute_command

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

There are no annotations, so the description carries full burden. It mentions 'via SSH' but does not disclose return format, permissions required, potential destructiveness of arbitrary commands, or that the command is executed as-is with no confirmation. This is a significant gap for a command execution 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 a single concise sentence that efficiently communicates the tool's core function. It is appropriately sized, though it could be slightly enriched with an example or cautionary note without becoming verbose.

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 command execution tool with no annotations, no output schema, and arbitrary command complexity, the description is too minimal. It does not address what the response looks like, how the command is delivered (e.g., SSH session handling), or any prerequisites beyond a device ID. This is inadequate for safe and correct invocation.

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%: both 'command' and 'device_id' have descriptions in the schema. The description adds no extra parameter-level detail, but the baseline of 3 applies since the schema already documents each parameter clearly.

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 a specific action: 'Execute a RouterOS command via SSH'. It identifies the resource (RouterOS) and the method (SSH), which distinguishes it from sibling command-execution tools like iot_execute_command or fortigate_execute_cli by scope.

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 explicit guidance on when to use this tool versus alternatives such as the mikrotik_get_* tools for read-only queries. Usage is implied as a generic command runner, but no exclusions or alternative references are given.

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