pip

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

With no annotations, the description must disclose behavior itself. 'Run an arbitrary uv pip command' hints at broad side effects but does not state that it can install, uninstall, modify environments, require permissions, or produce variable outputs, leaving the agent without critical safety context.

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, front-loaded sentence with no filler. It communicates the core action efficiently, though it is slightly under-specified rather than economically complete.

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?

Despite an output schema being present, the description omits essential context for an arbitrary-command tool: no mention of side effects, environment changes, or preference for specialized siblings. Without this, an agent cannot fully judge the tool's impact or appropriate use.

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 already fully documents the sole parameter (command) as 'Arguments passed after uv pip', and schema coverage is 100%. The description adds no additional semantic meaning beyond what the schema provides, so the baseline score of 3 applies.

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 uses a specific verb ('Run') and identifies the resource ('uv pip command'), clearly stating the tool's function. The word 'arbitrary' differentiates it from specialized sibling tools like pip_install or pip_list, signaling it is a generic passthrough.

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?

No guidance is given on when to use this generic passthrough versus the many dedicated sibling tools. The description does not mention preferring pip_install for installs, pip_uninstall for removals, or warn about using arbitrary commands.

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