pmg_apt_changelog

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

Given no annotations, the description carries full burden. It declares the tool as READ-ONLY, notes the content is upstream-authored and classified as ADVERSARIAL (taint.ADVERSARIAL_TOOLS), and clarifies that the API does not expose upgrade execution. This is thorough, though it could mention potential size limits.

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?

The description is concise and front-loaded with the READ-ONLY tag and endpoint. However, terms like 'smoke-confirm' and 'shape not live-verified' are somewhat cryptic and may reduce clarity for some agents.

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?

Given no annotations and presence of an output schema, the description adequately covers the return value (text), its adversarial nature, and configuration needs. It lacks details on error handling or missing packages, but overall is sufficient for tool selection.

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 the description adds value by explaining that 'name' comes from pmg_apt_updates_list, 'node' defaults to configured node, and 'proximo_target' is for multi-target config. This goes beyond the schema alone, aiding correct usage.

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?

The description clearly states it is READ-ONLY for fetching a package's changelog text on a PMG node. It specifies the endpoint pattern and distinguishes from sibling tools like pve_apt_changelog and pbs_apt_changelog, making the purpose unambiguous.

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?

The description indicates it is for visibility only, not execution, and references pmg_apt_updates_list for package names. It implies when to use (after listing updates) but does not explicitly state when not to use or suggest alternatives, leaving some gap.

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