get_system_info

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

No annotations provided, so the description carries the full burden. It states 'Retrieve' implying a read-only operation, but does not disclose other behavioral traits such as authorization needs, rate limits, or data freshness. For a simple retrieval tool, it is passable but not transparent.

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 two sentences: one stating the purpose, one detailing the return type. No unnecessary words, front-loaded with the action, and efficiently structured.

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 zero parameters and an output schema that exists (though not shown), the description adds value by stating the return type (dict[str, str]). It is adequately complete for a simple info tool, though it could mention potential errors or data freshness.

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, and schema coverage is 100% (no params). The baseline for 0 parameters is 4. The description does not need to add parameter info, so it meets the baseline.

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 'Retrieve system information including OS, CPU, and memory details.' It uses a specific verb ('Retrieve') and resource ('system information'), and lists key components. With no sibling tools, differentiation is not needed.

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 on when to use this tool or any prerequisites. While the purpose is straightforward, the description lacks explicit usage context or alternatives, so it's merely adequate.

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