system_info_tool

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 does mention what the tool returns ("System details including version, storage, registries, and runtime"), which gives some expectation of output. However, it omits explicit read-only safety, potential errors, or any operational nuances. It is adequate but not rich.

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 concise and front-loaded: a single clear action sentence followed by a short return summary. Every word earns its place, with no fluff or repetition.

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 tool's low complexity (zero parameters) and the presence of an output schema, the description is reasonably complete. It lists key return categories, and the output schema covers structured details. It doesn't explicitly state read-only behavior, but that is implied by the nature of the tool and is not critical when an output schema exists.

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, so the schema already fully documents the input (none). The description doesn't need to add parameter meaning. The baseline of 4 applies because no parameter documentation is required, and the description correctly implies that no inputs are needed.

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's purpose: "Get Podman system information." It further specifies the scope with "including version, storage, registries, and runtime," which adds concreteness. However, it does not explicitly differentiate from the sibling system_df_tool, though that tool is narrower in scope.

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 provided on when to use this tool versus alternatives. There is no mention of situations where system info is needed, nor any contrast with related tools like system_df_tool. The description simply states what it does without usage context.

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