get_system_info

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

There are no annotations, so the description must carry the full burden. It clearly describes what the tool returns and implies a read-only, non-mutating operation. It does not explicitly state that it never modifies anything or mention permissions, but for a system-info tool the behavior is well conveyed by the phrase 'GET COMPREHENSIVE SYSTEM INFORMATION' and the list of returned data.

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 front-loaded with the core statement, but it repeats itself through a keyword list and a full bilingual (Chinese) version. The keywords like 'system info, hardware, specs, os info, cpu, memory, ram, gpu' add little value for an AI agent and could be removed for conciseness. It is not tight; approximately half the content is redundant.

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 that the tool has no parameters and an output schema is present, the description only needs to explain what the tool does and when to use it. It does both thoroughly, covering the full scope of system information returned. No gaps remain for a tool of this simplicity.

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 baseline is 4. The description correctly adds no parameter-specific syntax since none exist. The input schema confirms 0 properties, so nothing more 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?

The description opens with 'GET COMPREHENSIVE SYSTEM INFORMATION about current machine' and explicitly lists the returned categories (OS, CPU, memory, GPU, network interfaces). This makes the tool's purpose unmistakable and distinguishes it from all sibling tools, which are file/command operations.

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 explicit use cases: 'checking system specs, verifying hardware capabilities, getting OS info, checking available resources.' It does not mention when-not-to-use or alternatives, but the sibling list contains no similar system-info tools, so this is clear enough. It could be a 5 if it explicitly excluded cases like performance benchmarking, but a 4 is fair.

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