sysknife_distrobox_list

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's 'read-only' (stated twice) is pure duplication. Beyond that it only says 'no params', which the empty schema already conveys; nothing is added about output shape, error behavior or what a distrobox listing contains.

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?

Very short and front-loaded with the action name followed by the purpose. It loses a little by restating 'read-only' at both the start and the end of a ten-word sentence, which is wasted space at this length.

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 read tool the description covers the essentials of what it does and that it is safe. However, with no output schema present, the description carries the burden of telling the agent what a listing returns (container names, images, status), and it says nothing about that.

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 takes zero parameters, so the baseline is 4. The description confirms 'no params', which is consistent with the empty schema and prevents an agent from hunting for undocumented arguments.

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?

States a specific verb and resource: 'list distrobox containers', plus the action identifier DistroboxList. The 'distrobox' qualifier meaningfully separates it from sibling listing tools such as sysknife_list_containers, sysknife_list_toolboxes and sysknife_multipass_list, though those siblings are never named.

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?

Usage is implied by the resource name — use it to enumerate distrobox containers — and 'no params; read-only' signals it is a safe discovery call. There is no explicit when-to-use/when-not guidance and no routing to the alternative container-listing siblings, so the agent must infer the choice.

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