execute_command

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

No annotations are provided, so the description carries the full burden. It discloses the platform shell and the 'allowed directory' scope, but it does not mention that commands can mutate the system, what permissions are used, how output/errors are returned, or whether execution is sandboxed.

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?

Two short sentences with the core action front-loaded and no filler. The platform detail earns its place by telling the agent which shell syntax to expect.

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 a powerful command-execution tool with no annotations and no output schema, this description is too thin. It omits return format, exit-code behavior, stderr handling, default working directory, timeout behavior, and what 'allowed directory' actually means in practice.

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 100%, with command, cwd, and timeout each described in the input schema. The prose adds little beyond the word 'shell command,' so it does not compensate for or improve on the schema, but it also does not need to.

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 ('Run') and resource ('shell command') and adds platform context (PowerShell on Windows, bash on Unix). It is clearly distinct from the sibling file, process, and system tools, even without naming an alternative.

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 about when to choose this tool over alternatives, nor any exclusions or prerequisites. The phrase 'allowed directory' implies a restriction but does not explain when a shell command is the right choice versus a more specific sibling tool.

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