runWait

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds a genuine precondition (trusted owner, interactive x64 desktop) not present in structured data, but says nothing about blocking behavior, exit codes, or what the launched process can affect.

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, no padding, with the platform scope front-loaded before the environment precondition. Efficient, though it is concise at the cost of substance rather than because it efficiently conveys a lot.

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 destructive, non-idempotent launch tool with no output schema, the description covers the environment requirement but omits the defining behavior (waiting for termination) and any return/exit-code expectations. Adequate as a minimum but leaves real gaps.

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 program, showFlag, and workingDir all documented in the schema itself. The description adds no parameter meaning beyond that, which matches the baseline 3 when the schema does the work.

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?

"Windows AutoIt runWait" largely restates the tool name and gives platform context, but never states the actual behavior (runs a program and blocks until it exits). It does not differentiate from siblings run, runAs, or runAsWait, so an agent must infer the blocking semantics from the name alone.

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 when-to-use guidance and no mention of alternatives like run (non-blocking) or runAsWait. The only stated condition, "requires a trusted owner and an interactive Windows x64 desktop," is an environmental prerequisite rather than routing guidance.

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