pve_apt_updates_list

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

Discloses read-only nature upfront, mentions it uses cached apt index, and describes expected response shape. However, lacks details on permissions or rate limits. With no annotations, description carries burden and does well but could be more comprehensive.

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?

Front-loaded with purpose and read-only flag. Some technical jargon (Smoke-confirm) may be unnecessary but overall efficient. Two paragraphs.

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?

Has output schema, so description doesn't need exhaustive return spec. Covers core purpose, usage, and limitations. Good for a simple list tool.

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%, but description adds context: defaults to configured node if omitted, and explains proximo_target for multi-target config. This adds value beyond schema defaults.

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?

Clearly states READ-ONLY and the action 'list available package updates' on a PVE node. Differentiates from sibling pve_apt_update_refresh by specifying it lists cached apt index.

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 tells when to use pve_apt_update_refresh first if list needs refreshing. Also warns that upgrades are not exposed via API, so tool only governs visibility.

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