iyke_pkg_uninstall

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

With no annotations, the description carries the full burden and discloses key behaviors: side effects (stops sidecars, removes registry, deletes files), what persists (project-scoped state), and exceptions (builtins blocked). Missing details on authorization or irreversibility, but largely transparent.

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 concise sentences front-load the main action and efficiently list consequences and exceptions with no unnecessary words.

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?

Covers major effects and constraints but omits important details like return value (or lack thereof), behavior on failure (e.g., unknown pkg_id), and the exact scope of 'project-scoped state'. Adequate but not comprehensive.

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 0% and the description adds no meaning to the 'pkg_id' parameter beyond its existence. It does not specify format, source, or validation, forcing the agent to rely on implicit knowledge.

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 'Uninstall a pkg' and enumerates specific actions (stop sidecars, remove registry entries, delete files), distinguishing itself from sibling tools like iyke_pkg_list. It also notes restrictions on builtins and surviving state, providing precise purpose.

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 implies when to use (to uninstall a package) and notes that builtins cannot be uninstalled, but it does not explicitly contrast with alternatives like iyke_pkg_list or provide scenarios for when not to use.

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