prioritize_process

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

No annotations provided, but description warns of unresponsiveness and advises sparing use. Could specify priority level or required privileges, but overall adequate.

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?

Concise: three lines purpose, then structured warning and usage conditions. Front-loaded and 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?

Covers purpose, usage, parameters, side effects, and return value. Complete for a single-parameter tool with no output schema.

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?

Target_pid is explained as 'Process ID to boost (REQUIRED).' Schema only gives type, so description adds needed context.

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 'Give a process HIGHER than normal CPU priority.' Specific verb+resource, and distinct from siblings like deprioritize_process and throttle_process.

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 lists three conditions for use: critical render deadline, system idle, and acceptance of risk. Also warns against frequent use.

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