tool_uninstall

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

The annotation destructiveHint=true already signals destructive behavior, and the description aligns with that. However, the description adds no extra behavioral context, such as irreversibility, side effects on dependencies, or confirmation requirements. It simply restates the action implied by the tool's name.

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, focused sentence with no redundant words. It immediately communicates the action and target, making it highly concise and effectively front-loaded.

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?

For a simple uninstall tool with one parameter, an output schema, and a destructive annotation, the description adequately covers the essential context: it operates on globally installed uv tools. It doesn't discuss return values, but that is handled by the output schema. The lack of explicit contrast with pip_uninstall is a minor gap, but the 'uv tool' qualifier provides sufficient distinction.

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 schema provides 100% coverage of the 'name' parameter with the description 'Tool name.' The tool description adds no further detail or example about the parameter, so it does not improve upon the schema's existing documentation.

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 globally installed uv tool,' using a specific verb and resource. It distinguishes itself from pip_uninstall by specifying 'uv tool' and 'globally installed,' 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 implies usage for uninstalling globally installed uv tools, but it does not explicitly explain when to use this over alternatives like pip_uninstall or mention any prerequisites. The guidance is inferred from the phrase 'uv tool' rather than stated directly.

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