pmg_apt_updates_list

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

With no annotations, description carries full burden. It states READ-ONLY, cached index, no upgrade execution, and that shape is not live-verified. Lacks details on rate limits or auth, but covers key behavioral traits.

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?

Concise, front-loaded with purpose. Includes HTTP endpoint which may be redundant but not harmful. No fluff; each sentence adds value.

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?

Complete for a simple tool with output schema. Covers purpose, read-only, cache, refresh dependency, config. Could mention staleness risk without refresh, but overall sufficient.

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 coverage is 100%, both parameters have descriptions. Description adds minimal value beyond schema (e.g., mentions {node} in endpoint). Baseline 3 is appropriate.

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?

Description clearly states 'list available package updates' on a PMG node, distinguishing it from sibling tools like pmg_apt_update_refresh (which refreshes the list) and apt tools for other products (pbs, pve). It emphasizes read-only and visibility-only scope.

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?

Explicitly recommends using pmg_apt_update_refresh to refresh the list first, and mentions config requirement (PROXIMO_PMG_*). No explicit exclusion for other apt list tools, but product-specific naming provides context.

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