Remote Execute

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

With no annotations, the description carries the full behavioral burden. It mentions a 'command policy' constraint, which is a small useful hint that execution may be filtered, but it omits side effects, permission/auth requirements, blocking/timeout behavior (the timeout_seconds param implies blocking), and what is returned.

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?

It is a single clean, front-loaded sentence with no filler or redundancy. Its brevity is appropriate in form even though the content is thin.

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 an execution tool with no annotations, no output schema, and 6 undocumented parameters, the description is far too sparse to let an agent call it safely. Nothing about side effects, return values, or parameter meaning is covered.

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% across 6 parameters, so the description is the only place semantics could be supplied, and it fails to name or explain any of them. 'Program arguments' loosely gestures at program and args, but project_id, environment, relative_cwd, and timeout_seconds are entirely 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 gives a verb ('Execute') and a resource ('structured program arguments under the remote project'), so the general purpose is discernible. However, 'structured program arguments' is jargon, and the description does nothing to separate this from the near-identical sibling ssh_execute, so an agent cannot tell the two apart from the text alone.

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?

There is no explicit guidance on when to use this tool versus alternatives such as ssh_execute, remote_apply_patch, or slurm_submit. The phrase 'under the remote project and command policy' hints at scoping but stops short of any when-to-use or when-not-to-use condition.

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