get_system_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies read-only behavior through the verb 'Get' but does not explicitly state that it has no side effects, does not mention the return format, and gives no platform-specific caveats or potential failure modes.

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 entire description is one short, front-loaded sentence that names the action and the key data categories with no filler or repetition. It is as concise as possible for a no-argument system information tool.

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?

For a zero-parameter tool this is minimally workable: an agent knows what the tool does and what high-level data to expect. However, because there is no output schema, the missing return-format description, error behavior, and platform details leave meaningful gaps for interpreting the result.

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 input schema has zero parameters, which earns a baseline of 4. The listed output categories in the description add mild value by setting expectations for the kind of data returned, and there are no parameter semantics left undocumented.

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 action ('Get') and the resource ('system info'), and enumerates the returned categories: OS, CPU, RAM, and disk. It is easy to tell this is a read-only system inspection tool, though it does not explicitly contrast itself with overlapping siblings like get_env or list_processes.

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 is given about when to prefer this tool over alternatives such as get_env, list_processes, or execute_command. The description simply restates what the tool does and leaves all selection reasoning to the agent.

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