get_system_info

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It states what information is returned but does not mention that gathering 'comprehensive' data may require elevated privileges, may be slow, may behave differently across OSes, or how failures in one subsystem are handled. For a tool with zero annotation coverage, this is a notable gap.

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 sentence where every word earns its place: the action, the scope, and the categories are all stated without redundancy. The category list is the only necessary elaboration and it is compact.

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?

The complexity is low (zero params, no nested objects), and the description names the broad return domains, which is partially adequate given there is no output schema. But it does not communicate the return shape, units, or how this aggregates/disitnguishes from the many sibling probes that cover the same domains (get_disk_usage, get_networ_connections, list_processes), leaving selection ambiguity unresolved.

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 zero parameters, so the schema (an empty object at 100% coverage) fully documents the input surface. Per the rubric, 0 params gets a baseline of 4; there is nothing more a description could meaningfully add about parameters.

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 names a specific verb ('Get') and resource ('comprehensive system information'), and enumerates the covered domains: CPU, memory, disk, and network. This is clear, but it does not explicitly contrast itself with overlapping siblings like get_disk_usage or get_network_connections; an agent must infer from 'comprehensive' that this is the aggregated superset.

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 term 'comprehensive' implies this is the broad-strokes overview tool, and the sibling list suggests more targeted alternatives exist. However, there is no explicit when-to-use / when-not-to-use statement, no named alternatives, and no guidance on whether to prefer this over the specific probes (e.g., get_disk_usage, list_processes) when onlyone subsystem is needed.

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