processSetPriority

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation risk is covered. The description does add non-annotation context — the trusted-owner requirement and the need for an interactive Windows x64 desktop — but says nothing about what happens to a process that does not exist, whether the change is reversible, or failure behavior.

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 with no filler, but the first sentence ('Windows AutoIt processSetPriority') duplicates the name instead of front-loading useful information. Structure is fine; content density is low.

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 mutation tool with no output schema, the description covers the environmental prerequisite but omits the practical essentials an agent needs — valid priority semantics, behavior when the target process is absent, and what the call returns or throws. Adequate but with clear 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%, so both parameters (process, priority) are already documented and the baseline is 3. The description adds no parameter meaning at all and notably does not reconcile the schema's 'Priority level (0-4)' hint with the much wider declared integer range.

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 leads with 'Windows AutoIt processSetPriority', which largely restates the tool name rather than articulating the action in plain terms (e.g., 'changes the scheduling priority of a running process'). The name is self-describing enough that an agent can infer the purpose, but the description itself adds only platform context, not a clearer verb+resource statement.

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 given on when to use this tool versus siblings like processExists, processClose, or run. The statement about a 'trusted owner' and 'interactive Windows x64 desktop' is a precondition, not a when-to-use rule, and no alternatives or exclusions are named.

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