Execute Remote Command

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

The description adds 'non-interactive' and 'policy and safety checks' beyond annotations (which show mutation but no idempotency or destructiveness). However, it omits failure behavior, side effects, or output 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 a single, focused sentence with no filler. It front-loads the essential action and key constraints.

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 complexity (5 parameters, nested objects, output schema), the description is too sparse. It lacks parameter usage hints and explanation of safety checks. The output schema reduces the need for return descriptions, but more detail would improve completeness.

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?

All 5 parameters are fully documented in the input schema (100% coverage). The description does not provide additional parameter-level guidance, so the baseline score of 3 applies.

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), the target (non-interactive command on remote system), and includes qualifiers (policy and safety checks). This distinguishes it from sibling tools like proc_exec_stream or proc_sudo.

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 non-interactive commands but does not explicitly contrast with siblings or provide when-to-use/when-not-to-use guidance. No alternative tool names are mentioned.

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