get_crictl_imagefsinfo

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

No annotations are provided, so the description must carry the full load. It usefully discloses that the tool runs over SSH against a remote Linux host and 'usually requires root', which is real operational context an agent needs. It does not state that the operation is read-only, what happens on hosts without a CRI runtime, or how SSH authentication failures surface, so important behavior remains undocumented.

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?

Two short sentences, with the resource and output fields front-loaded before the usage directive. There is no filler, although the parenthetical field list is slightly dense and the SSH detail could be tightened.

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?

An output schema exists, so the description need not explain return values, and it correctly doesn't. However, with 7 undocumented parameters, no annotations, and SSH connection semantics only partially covered, the definition leaves too much for the agent to infer when constructing a valid call.

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?

Schema description coverage is 0% across 7 parameters. The description implies host and the SSH credential parameters (key_path, password, root), but it says nothing about port, timeout, or accept_new_hostkey. Several parameters therefore remain completely undocumented at both the schema and description level, so the description does not compensate for the coverage gap.

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 states a specific verb and resource: it collects crictl imagefsinfo output, and it enumerates what that output contains (mountpoint, used bytes, inodes of the CRI image filesystem on a Kubernetes node). That is far more concrete than the tool name alone. It does not explicitly distinguish this tool from nearby siblings such as get_crictl_images or get_inode_usage, so it falls short of a 5.

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 gives explicit when-to-use guidance: 'USE THIS TOOL to investigate image garbage collection and DiskPressure', which is a concrete diagnostic scenario. The main gap is that it names no alternative (for example, get_crictl_images or get_disk_usage) and sets no exclusions, so the agent must infer when another tool is the better choice.

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