milehost_exec_command

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

With no annotations, the description carries the full behavioral burden. It discloses that the command runs directly inside the container, but it does not warn that arbitrary shell commands can mutate the container state, delete data, or require specific permissions. For a remote-execution tool, this lack of side-effect disclosure is a significant gap.

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 first sentence is concise and informative, but the second sentence is largely redundant with the first. It adds an emphatic directive without new information, so it does not fully earn its place.

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 potentially destructive remote-command tool with no annotations and no output schema, the description is too sparse. An agent is not told about authentication requirements, whether folder_id is needed for multi-server setups, what the response contains, or what safety considerations apply. The presence of multiple similarly named sibling tools makes this gap more serious.

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%, so the input schema already explains command, api_key, api_url, and folder_id. The description adds no parameter-level details, which is acceptable under the baseline since the schema handles the heavy lifting.

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 (executes a terminal/shell command), the resource (remote cloud Docker container on MileHost), and the execution location (directly inside the container). However, it does not differentiate this tool from sibling tools like milehost_run_command and milehost-run-command, which appear to have nearly identical purposes.

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 'AI AGENT MANDATE' sentence tells the agent to use this tool for running commands directly inside the cloud container, which is a usable usage signal. But it mostly restates the purpose and does not explain when not to use it, when to prefer a sibling command tool, or what prerequisites must be met.

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