sysknife_list_flatpak_remotes

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, so the safety profile is fully covered. The description's 'Read-only' merely restates readOnlyHint and adds nothing about output shape, whether system and per-user remotes are both included, or permission needs.

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, but the opening clause 'Read-only SysKnife action `ListFlatpakRemotes`' repeats the tool name and the readOnlyHint annotation, spending words on no new information.

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 zero-parameter read tool with rich annotations and no output schema, the description is minimally adequate. However, the stray 'username*' mention without schema backing and the absence of any note on what a 'remote' entry contains leave small but real gaps.

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 no properties, so the baseline is 4, but the description introduces 'param: username*' — a parameter that does not appear in the schema and whose asterisk implies required, contradicting 'Required parameters: 0'. This adds a hint about scoping remotes by user, but the inconsistency muddies rather than clarifies.

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 configured Flatpak remotes'. An agent can distinguish it from siblings like sysknife_list_installed_flatpaks (installed apps) and sysknife_search_flatpak_apps (search) without opening schemas. It does not explicitly name those siblings, keeping it at 4.

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 or when-not-to-use guidance, and no alternatives are named. The verb 'list' implies a read operation, but the agent must infer that this is for inspecting remote repositories rather than installed apps.

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