Get WSL system information

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

The annotations include readOnlyHint: true, indicating this is a safe read operation. The description doesn't contradict this, as 'Get' aligns with read-only behavior. However, it adds no behavioral context beyond what annotations provide—such as what specific information is returned, potential rate limits, or authentication needs. With annotations covering the safety profile, the description adds minimal value, meeting the baseline for this dimension.

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 extremely concise—a single phrase with no wasted words. It's front-loaded and to the point, which is efficient for a simple tool. However, it's arguably too concise, bordering on under-specification, as it sacrifices clarity for brevity. This earns a high score for conciseness but not a perfect 5 due to the trade-off with completeness.

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 (0 parameters, read-only annotations) and lack of an output schema, the description is incomplete. It doesn't explain what 'system information' entails (e.g., WSL version, distribution details, or hardware info), leaving the agent uncertain about the return values. With no output schema, the description should provide more context on the expected data, but it fails to do so, making it inadequate for full understanding.

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 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to compensate for any gaps, as the schema fully handles the lack of inputs. This justifies a baseline score of 4, as the description isn't required to add parameter semantics in this case.

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?

Tautological: description restates name/title.

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 provides no guidance on when to use this tool versus alternatives. It doesn't specify what type of system information it retrieves (e.g., OS details, version, configuration) compared to siblings like get_disk_usage or list_processes, leaving the agent to guess based on the tool name alone. There are no explicit instructions on context or exclusions, resulting in poor usage guidance.

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