Inspect Windows system

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safe read-only behavior. The description adds 'without changing the PC' which reinforces this and provides a list of information categories returned. No contradiction exists.

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?

The description is a single, front-loaded sentence that efficiently states the tool's purpose and resource scope without any wasted words or redundancy.

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 zero-parameter, read-only system information tool with good annotations, the description is complete. It lists the information categories and explicitly confirms no side effects. An output schema is absent but not necessary given the explanatory list of returned data.

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 coverage is 100% with zero parameters, so the description has no additional burden to explain parameters. The description adds value by enumerating the specific categories of information returned, which helps the agent understand what to expect.

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 specifies a clear verb 'Return' and lists the exact resources: local Windows, CPU, memory, user, host, runtime, and server capability information. It also explicitly states the tool does not change the PC, which distinguishes it from mutation tools like file_operation or write_file.

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?

The description states it 'does not change the PC', implying it is safe to use for inspection without side effects. However, it does not explicitly mention when not to use it or name alternatives among sibling tools such as path_info or list_windows for more specific diagnostics.

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