windows_system_info

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

No annotations are supplied, so the description carries the full behavioral burden and does not state that this is a read-only, side-effect-free probe, nor anything about latency, permissions, or freshness of the values. It only names returned fields, which the output schema already covers.

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?

A single front-loaded fragment with zero padding; every listed item is a real returned field. It is arguably too terse rather than too long, so it loses a point for under-specification rather than verbosity.

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?

With no parameters and a full output schema, the description only needs to say what domain the tool reports on, and it does. The main omission is any statement of read-only safety and freshness, which matters when annotations are absent.

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 takes zero parameters, so the baseline is 4 and there is nothing the description could add about argument meaning. It correctly avoids inventing filter options that do not exist.

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 enumerates the specific resource contents (OS name/version, hostname, boot time, memory totals), which makes the tool's function unambiguous despite lacking an explicit verb. It is not a tautology of the name, but it never contrasts itself with siblings like read_eventlog or list_windows_processes.

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?

Usage is only implied: an agent can infer this is the go-to tool for host identity and capacity facts. There is no explicit when-to-use statement, no exclusions, and no mention of alternatives for overlapping questions such as event-log-derived boot times.

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