run_shell_command

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

Without annotations, the description only notes that the command uses the default interpreter, omitting safety-critical details like potential system impact, required permissions, or return/error behavior. For a command execution tool, this is a significant transparency 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 description is compact and front-loaded with the purpose, followed by a clear Args list. Every sentence contributes, with no redundant boilerplate.

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 can execute arbitrary shell commands, the description is minimal: it does not address output format, error handling, security implications, or what 'running agent' means precisely. Sibling tools with specialized purposes underscore the need for more context.

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 Args section provides definitions for both agent_id and command_line, adding meaning beyond bare schema type information. However, it lacks details like command syntax, quoting rules, or constraints, leaving the agent to guess at proper usage.

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 uses a specific verb 'Execute' with a clear resource 'a running agent', stating the tool runs a shell command line. It distinguishes itself from specialized siblings like execute_powershell by specifying the default command line interpreter.

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 guidance on when to use this tool versus alternatives such as execute_powershell or run_as_user. The description only states what the tool does, leaving usage context to be inferred without explicit when/when-not guidance.

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