win_get_system_info

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

With no annotations, the description carries full behavioral burden. 'Get' implies a read, but there is no disclosure of required credentials (notable given the win_setup_credentials sibling), permissions, latency, or output shape. The agent knows only that it is likely non-mutating.

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?

One short, front-loaded sentence with no filler, which is appropriate. However, brevity here comes at the cost of specification rather than earned conciseness.

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 remote-host read tool with no output schema and no annotations, the description omits the essentials: what information is returned, authentication requirements, and hostname semantics. Only the bare purpose is covered.

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 description coverage is 0% and the single required parameter 'hostname' is never mentioned in the description. No format, target eligibility, or default behavior is conveyed, so the agent must infer parameter meaning entirely.

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?

States a verb and resource ('Get basic system information from Windows host'), and the resource is distinct from siblings like disk space or running services. But 'basic system information' is vague about what is actually retrieved (OS version, uptime, hardware?), leaving the agent guessing at scope.

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?

No indication of when to use this over siblings such as win_get_disk_space or win_get_running_services, nor any prerequisites. The agent gets a label, not routing guidance.

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