pip_uninstall

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

Annotations already provide destructiveHint=true, so the destructive nature is known. However, the description adds no additional behavioral context beyond the annotation—no mention of environment effects, reversibility, or error outcomes. It simply restates the action.

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 a single, concise sentence that conveys the essential function without redundancy. It is appropriately sized for a simple tool, with no wasted 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?

Given the simple tool with only two parameters and an output schema, the description is minimally adequate. However, it does not clarify the default target virtual environment (venv_path optional) or differentiate from similar tools like 'remove', leaving some ambiguity in context.

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?

The input schema describes both parameters (package_name and venv_path) with 100% coverage. The description does not add any parameter-specific meaning, but since the schema already carries the full documentation, the 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?

The description clearly states the action (uninstall), the object (a package), and the method (using uv pip). This is specific enough to distinguish it from pip_install and other pip subcommands, satisfying the verb+resource+mechanism criterion.

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 offers no guidance on when to use this tool versus alternatives like pip_install, remove, or pip_sync. It lacks any context about prerequisites, target environment selection, or exclusions, leaving the agent without decision support.

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