python_venv

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

With no annotations, the description should disclose behavioral traits. It only lists actions without explaining side effects (e.g., create impacts filesystem, delete removes directory). The 'clear' parameter hints at destruction but is not described in the description.

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 listing actions, which is efficient. However, it could be improved by front-loading the core purpose more structurally, e.g., separating action descriptions.

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 8 parameters and no output schema, the description is too brief. It does not explain return values for 'info' or 'list', nor how to use parameters like 'venvPath' or 'systemSitePackages' with actions. A more detailed description would be beneficial.

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 100%, so the baseline is 3. The description does not add meaning beyond the schema; it merely summarizes the actions. For example, it doesn't explain how 'args' or 'python' relate to actions.

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 tool manages Python virtual environments and lists the specific actions (create, delete, info, list packages), using a specific verb and resource. It distinguishes itself from sibling tools like python_install_deps or python_build as it focuses on venv management.

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 provided on when to use this tool versus alternatives (e.g., using system python or other sibling tools). There is no mention of prerequisites or context for any action.

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