get_system_info

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

No annotations exist, so the description must bear the full burden. It implies a read-only query by listing output fields, but does not explicitly state it is non-destructive, requires no elevation, or has no side effects. For a zero-parameter tool, this is minimally adequate but not rich.

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 short sentence listing key attributes. It is front-loaded and contains no fluff. Every word earns its place, making it easy to scan.

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?

Without an output schema, the description should ideally clarify the return format (e.g., JSON object, structured data). It only lists attribute categories, not their types or structure. For a simple tool this may suffice, but it leaves ambiguity about how data is organized.

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?

There are zero parameters, so the description has no burden to explain them. The schema coverage is 100% by default. The description instead focuses on output fields, which is appropriate. No param information is needed.

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?

Description lists specific OS and system attributes (build, architecture, hostname, AV, PowerShell version), clearly indicating the tool retrieves system information. The verb 'get' in the name reinforces this. While it distinguishes from sibling tools like 'list_processes' or 'get_network_connections' by specifying these exact fields, it does not explicitly state an action verb like 'retrieves' in the description.

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 guidance is provided on when to use this tool versus siblings. It simply lists the data returned. There is no indication of prerequisites, contexts, or alternatives, which is a significant gap given 17 sibling tools with overlapping purposes.

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