execute_powershell

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

The only behavioral disclosure is 'Windows only'. With no annotations provided, the description carries full burden but fails to mention whether execution is blocking, error handling, or authorization needs. For a code execution tool, far more transparency is required.

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 with two lines: the first line states purpose, the second gives an example. No wasted words; front-loaded with core behavior.

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?

Despite having an output schema, the description omits crucial context: it does not mention that execution targets an agent via agent_id, nor does it discuss output structure, timeouts, or security implications. A PowerShell execution tool needs more completeness.

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 description adds meaning for the 'command' parameter by giving an example but does not describe 'agent_id' at all. Since schema description coverage is 0%, the description partially compensates but is incomplete.

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 'Execute a PowerShell expression (Windows only)', which is a specific verb and resource. It distinguishes from sibling tools like execute_shell or execute_raw by specifying PowerShell and Windows-only constraint.

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 on when to use this tool versus alternatives such as execute_shell or execute_raw. The description merely states it executes a PowerShell expression, leaving the agent to infer usage context without explicit when-to-use or when-not-to-use advice.

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