sysknife_snap_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' adds no information beyond structured fields. It says nothing about output shape, ordering, or whether it covers only installed snaps versus all known snaps.

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 useful content. It loses a point for restating 'read-only' twice (once at the start, once at the end) — the trailing repetition earns nothing.

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?

A zero-parameter, read-only listing tool whose safety profile is fully covered by annotations; the description is sufficient to call it correctly. Only the missing distinction from the sibling snap_info tool keeps it from a 5.

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?

There are zero parameters, so the baseline is 4. The description's 'no params' correctly confirms the tool takes no arguments, matching the empty schema.

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?

Names a specific verb and resource — 'list installed snaps' — so the agent knows exactly what it returns. It does not differentiate from the near-identical sibling sysknife_snap_info (single-snap details) in the large sibling set, leaving that inference to the agent.

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 when-to-use context, no exclusions, and no routing to alternatives such as sysknife_snap_info or the flatpak listing tools. The only guidance is the implicit 'no params' hint for invocation.

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