mikrotik_ssh_custom

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

No annotations exist, so the description bears full responsibility. It states the tool executes commands via SSH but reveals no behavioral traits such as potential destructiveness, authentication needs, or output format. This is inadequate for safe invocation.

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, but it is too brief to provide sufficient information. It omits critical details that could be included without significant length increase, balancing conciseness with completeness.

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 nature (custom command execution), the lack of annotations, output schema, and parameter descriptions, the description is severely incomplete. It fails to clarify safe usage, return values, or the meaning of 'identifier', leaving the agent underinformed.

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 0% description coverage and the tool description adds no meaning to the parameters 'identifier' and 'command' beyond their names. The agent is left to infer what 'identifier' refers to (e.g., device IP/hostname) and what commands are acceptable.

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 ('execute custom MikroTik command via SSH') and the target resource (MikroTik device). However, it does not distinguish this from sibling tools like 'send_custom_command' which also perform custom commands on other platforms, leaving ambiguity about 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 guidance is provided on when to use this tool versus alternatives (e.g., specialized 'get_mikrotik_*' tools or 'send_custom_command'). No prerequisites or exclusions are mentioned, leaving the AI agent without sufficient context for correct selection.

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