run_powershell

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

There are no annotations, so the description carries the full behavioral disclosure burden. It only says the command is 'restricted' but does not explain what restrictions apply, whether execution is sandboxed, whether side effects are possible, or how output is returned. 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 a single efficient sentence with no filler. It front-loads the operation and adds useful qualifiers like 'restricted' and 'development command' while remaining compact, though it is too sparse to be fully informative.

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?

The tool executes arbitrary commands, which is high-risk and context-dependent, yet the description provides no details about restrictions, expected use cases, or behavioral limitations. Even with an output schema present, the lack of any guidance around command selection, permissions, or failure modes makes this incomplete.

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 explain any of the three parameters. The agent is left to infer the meaning of command, timeout_seconds, and working_directory solely from their names and types. The description adds no parameter-level meaning beyond what the schema already exposes.

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 tool runs a PowerShell command, identifies the platform as Windows, and narrows scope to 'development' commands. It distinguishes itself from sibling file, build, and network tools, though 'restricted' is somewhat vague.

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 explicit guidance is given about when to use this tool versus alternatives such as build_project, compile_shader, or get_system_info. The phrase 'development command' weakly implies a context, but there are no conditions, exclusions, or alternative tool mentions.

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