run_as_admin

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

Discloses platform restriction, admin privilege requirement, and user approval step. However, with no annotations provided, the description does not cover failure behaviors, return value, or execution model (synchronous/asynchronous), which are relevant for a mutation tool.

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?

Single sentence, front-loaded with key constraint (Windows only), no redundant information. Every word adds value.

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 single-parameter tool with no annotations and no output schema, the description covers platform, privilege, and approval but omits execution details (e.g., success/failure, output format). Could be more complete.

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 covers 100% of parameters with description matching command semantics. Description adds no additional meaning beyond what the schema already provides.

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?

Description clearly states it executes a PowerShell command with Administrator privileges, specifies Windows-only and visual user approval. Distinguishes from sibling run_as_root by platform and privilege model.

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?

Implicitly indicates Windows-only usage and differentiation from run_as_root, but lacks explicit when-to-use, when-not-to-use, or alternative guidance. No mention of scenarios requiring admin vs standard execution.

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