Inspect Windows system

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

The description adds a clear non-destructive guarantee ('without changing the PC'), which complements the readOnlyHint and destructiveHint annotations. While it doesn't discuss permissions or side effects, the core behavioral trait is transparently disclosed.

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, concise sentence that efficiently lists the categories of information returned. There is no superfluous text or ambiguity in structure.

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?

Given the tool's simplicity and lack of output schema, the description fully covers its purpose and safety behavior. It clearly outlines what the user can expect without needing additional details.

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?

The tool has no input parameters, and the description appropriately avoids discussing them. Since there are no params, the baseline is 4; the description adds value by specifying what kind of information is returned, which is more than sufficient.

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 clearly states the tool returns system information (Windows, CPU, memory, user, host, runtime, server capability) and explicitly notes it does so without changing the PC. This is specific and distinguishes it from sibling tools like exec or file operations.

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 implies safe usage ('without changing the PC') but does not explicitly state when to use this tool versus alternatives. It lacks direct comparison to other tools or scenarios, leaving the usage context implicit.

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