System Hardware

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not that this is a read-only query, not that the NAS host/port/profile parameters imply an authenticated session, not what hardware categories are returned. One generic sentence is inadequate for an unannotated tool.

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 short sentence with no filler, which is structurally clean and front-loaded. But brevity here comes from under-specification rather than discipline, so it earns only a middling score.

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?

An output schema exists, so return values need not be explained, but for a 4-parameter tool with zero annotations the description should at least establish scope, read-only nature, and how it differs from system_info/system_details. None of that is present.

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 100% — host, port, scheme, and profile are all documented in the schema itself, including the port examples and the default-profile behavior. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 states a verb and resource ('获取硬件信息' / get hardware information), so the basic purpose is legible. However, it does not differentiate this tool from closely related siblings such as system_info, system_details, storage_overview, or the monitor_cpu/monitor_memory family, leaving the agent unable to tell what 'hardware' specifically covers.

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?

There is no indication of when to use this tool versus system_info, system_details, or the individual monitor_* tools. No prerequisites, no exclusions, no routing guidance of any kind.

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