Start background PowerShell job

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

Annotations already indicate destructiveHint=true. The description adds context about background execution and persistent logs, but does not elaborate on potential side effects or non-blocking behavior beyond the annotation. It provides some value without contradiction.

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 clear, concise sentences that convey the core action, key behavior (background, logs), and usage guidance. No wasted words.

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?

Provides good high-level context (long-running, background, logs, polling advice) but omits how the job ID is returned or how to reference the job with job_status. Since there is no output schema, this is not strictly required, but it would improve usability.

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 schema has no per-parameter descriptions. The description mentions 'PowerShell command' (implying the 'command' parameter) but does not explain the purpose of 'cwd' or 'label'. With 0% schema coverage, it should compensate but fails to describe two of three parameters.

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?

Clearly states that it starts a long-running PowerShell command in the background with persistent logs, distinguishing it from synchronous execution (exec) and monitoring (job_status).

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?

Explicitly advises polling with job_status instead of waiting in exec, giving a clear alternative and implied use case for long-running tasks. Could be stronger by stating when not to use this tool (e.g., for quick commands).

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