get_system_info

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

No annotations provided. The description describes a read operation ('Get') but does not explicitly state read-only nature, error conditions, or any side effects. It minimally discloses the returned information.

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, comprehensive sentence that immediately conveys the purpose and output. No wasted words.

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 (no parameters, no nested objects, and no output schema), the description sufficiently covers what the tool returns. It could mention response format, but not critical for this straightforward 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 no parameters (0 params, schema coverage 100%). Baseline is 4. The description adds no parameter info but lists the output, which is acceptable given no parameters exist.

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 'Get basic system information' and lists specific fields (hostname, OS, kernel version, architecture). This distinguishes it from sibling tools which focus on metrics (CPU, memory, etc.).

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 implies usage for retrieving system info but does not explicitly state when to use versus alternatives or provide any exclusions. Siblings are metrics tools, so context is clear but no direct guidance.

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