sysknife_ubuntu_list_flatpaks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, and the description only restates 'read-only' twice. It adds no context about scope (system vs. per-user Flatpaks), permissions needed, or result shape that would go beyond the structured fields.

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, but 'Read-only' is stated twice in one sentence and the backticked internal action name `UbuntuListFlatpaks` consumes space without adding meaning for a caller. The bogus `username*` token is noise that must be parsed and discarded.

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 simple idempotent read with full annotation coverage, the description is close to sufficient, but the invented `username*` parameter and the lack of differentiation from `sysknife_list_installed_flatpaks` leave an agent with open questions before invoking it.

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 schema declares zero properties (additionalProperties: true), yet the description advertises 'param: username*' as if a required username existed. That phantom parameter contradicts the schema and would lead an agent to pass an argument nothing documents, rather than clarifying the (nonexistent) inputs.

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 installed Flatpak apps', which is clearly a read operation. However, it does not distinguish itself from the near-identical sibling `sysknife_list_installed_flatpaks` (nor from `sysknife_get_flatpak_app_info` / `sysknife_search_flatpak_apps`), leaving an agent unable to choose between them from the description alone.

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, when-not-to-use, or alternative guidance is given. With a sibling named `list_installed_flatpaks` that appears to do the same thing, the absence of any disambiguation is a real selection hazard rather than a minor omission.

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