get_system_info

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

The description indicates a read-only operation ('Get'), but with no annotations, it lacks details on potential side effects, required permissions, or error conditions. The simple nature of the tool reduces the need for extensive disclosure, but a statement about being non-destructive would be helpful.

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, efficient sentence (15 words) with no superfluous information. It is front-loaded with the action and key outputs.

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 the simplicity of the tool (no parameters, output schema exists), the description provides a solid list of return values. It could be enhanced by noting any prerequisites or that it requires no user input, but it is sufficient for a straightforward info retrieval tool.

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 cannot add meaning beyond the empty schema. However, it lists the returned fields, which provides context for what the tool outputs; this exceeds the baseline for no-parameter tools.

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 clearly states the tool gets specific system information: NAS model, DSM version, hostname, uptime, RAM, temperature, and serial number. It uses a specific verb ('Get') and resource ('system info'), and it distinguishes itself from sibling tools like get_disk_info and get_network_info by covering a broader set of attributes.

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 explicit guidance on when to use this tool versus sibling tools. While the broad scope implies it is for a general system overview, a brief note clarifying that it aggregates multiple hardware and software details would improve decision-making.

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