shell_exec

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

Without annotations, the description carries full burden. It discloses returning combined stdout/stderr and warns about full system access, but lacks details on error handling, blocking behavior, environment variables, or interactive commands. More transparency would be beneficial for a high-risk tool.

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 extremely concise (two sentences) and front-loaded with the core action. Every word adds value with no filler.

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 high risk and lack of output schema, the description is brief. It could include more about security implications, timeout behavior, and error handling. However, it adequately sets context for a shell execution tool among file-focused siblings.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning to the parameters beyond what the schema provides. No parameter-specific information is given.

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 states a specific action ('Run a shell command'), identifies the resource ('host machine'), and explains the output ('combined stdout/stderr'). It also clearly distinguishes from sibling tools (all file/system operations) by highlighting the shell execution capability.

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 shell commands but lacks explicit guidance on when to use vs. alternatives. The 'Full system access' warning hints at caution but does not provide explicit when-not-to-use scenarios or alternatives (though siblings are file-focused).

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