run_shell

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'run a PowerShell command' but fails to mention side effects, security implications, permission requirements, output/error handling, or whether the command executes synchronously. For a shell execution tool, this is a critical 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 a single sentence, which is concise in length but under-specified for the complexity of the tool. It lacks necessary details and is closer to an under-specification than a model of conciseness. The sentence is front-loaded, but the brevity detracts from its utility.

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 shell execution tool with no annotations, two parameters, and no description of return values or side effects, this description is completely inadequate. Even with an output schema, the description fails to provide essential context about when to use it, what to expect, or how parameters affect execution.

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%, and the description does not compensate. It does not mention the 'command' parameter or the 'cwd' parameter, nor does it explain defaults, formatting, or how the command is interpreted. The agent is left with no semantic understanding beyond parameter names.

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') and a specific resource ('a PowerShell command on the user's machine'), which clearly differentiates it from siblings like run_python (Python) and run_cpp (C++). The explicit mention of 'PowerShell' distinguishes it from generic run_code or run_file, giving it a clear scope.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or complementary tools. The description simply states what it does, leaving the agent to infer usage context.

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