apt_upgrade

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

No annotations are present, so the description must disclose behavioral traits. It only states 'upgrade all packages' without mentioning required permissions (sudo), potential side effects (service restarts), or that it modifies system state. The destructive nature is implied but not clarified.

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?

Two sentences front-load the key action and prerequisite. It is concise and clear, but could be slightly more informative without losing efficiency.

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 output schema and only partial parameter descriptions, the description does not explain return values or behavior. The agent lacks context on what happens after upgrade (e.g., reboot needed) and how parameters affect execution.

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 description coverage is 33% (only autoRemove has a description). The tool description adds no information about parameters, leaving the agent without guidance on meaning of alias or sudo_password. With low coverage, the description should compensate but does not.

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 'Upgrade all packages (apt upgrade)' with a specific verb and resource, and distinguishes from sibling tools like apt_install and apt_update by implying it is the upgrade step.

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 instructs to 'Use apt_update first', providing a clear prerequisite. However, it does not specify when not to use this tool (e.g., when only security updates are needed, alternatives like check_updates_security exist).

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