podman_system_df

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds minimal extra behavioral context—just 'disk usage statistics'—but does not elaborate on what scopes are covered (e.g., containers, images, volumes) or the nature of the output. It does not contradict the annotations.

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 short sentence with no unnecessary words. It is concise and straight to the point, containing the core meaning without redundancy.

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 read-only, zero-parameter tool, the description is minimally adequate but sparse. It does not specify which disk usage categories are included (e.g., container, images, volumes) or mention that it provides a system-wide summary. However, given the tool's simplicity and available output schema, the description meets the baseline but leaves room for richer context.

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 input schema is trivially 100% covered. The 0-parameter baseline applies, and the description need not explain any parameter details.

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 '磁碟用量統計 (podman system df)' clearly identifies that the tool provides disk usage statistics, which is a specific and distinct function among the sibling tools. It goes beyond merely restating the tool name, though it could be more action-oriented (e.g., 'list' or 'show').

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 offers no guidance on when to use this tool versus alternatives such as podman_info or podman_images. There is no mention of context, prerequisites, or exclusions.

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