remote_execute

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

With no annotations, the description discloses short-lived connection lifecycle, protocol support (SSH/WinRM), WinRM shell options, and SSH shell behavior. This is meaningful behavioral context, though it omits security and failure-mode details.

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 four sentences with a small JSON example. Every sentence adds relevant detail, and the purpose is front-loaded without fluff.

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 complexity of 8 parameters, no annotations, and 0% schema coverage, the description is under-specified. It covers connection and shell details but misses usage guidance and most parameter semantics, despite the output schema covering return values.

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 0%, so the description must compensate. It explains only the connection parameter with an example and mentions shell semantics, but command, profile, timeout, output_limit, cwd, and env are left undocumented.

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 'Execute one command using a short-lived SSH or WinRM connection,' specifying the action, resource, and transient nature. This distinguishes it from session-based tools like remote_session_execute and long-running job tools.

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 implies usage for one-off command execution and explains connection/profile override, but it does not explicitly state when to prefer this tool over alternatives like remote_session_execute or remote_job_start, nor does it provide exclusions.

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