create_virtualenv

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

No annotations are provided, so the description must fully disclose behavior. It states 'Create a virtual environment and optionally install packages,' which indicates a mutating action but does not explain what happens if the path already exists, which Python version is used, or any other side effects or requirements.

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 conveys the primary purpose and optional behavior in ten words, with every word earning its place.

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?

The tool is low-complexity with two parameters and an output schema, so a concise description could be sufficient. However, the description lacks any contextual guidance on when to use it relative to the many sibling tools and does not mention potential edge cases, making it only minimally adequate.

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 covers 100% of parameters with clear descriptions ('Environment path.' and 'Optional packages to install.'), so the baseline is 3. The description's mention of 'optionally install packages' mirrors the schema and adds no new semantic detail.

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 'create' and identifies the resource 'virtual environment', clearly distinguishing it from sibling tools focused on dependencies, building, or Python version management. It also adds the optional package-install behavior, which goes beyond the tool's name to clarify its functionality.

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 provides no guidance on when to use this tool versus alternatives like 'init', 'build', or 'python_install'. There is no mention of scenarios, prerequisites, or exclusions, leaving the agent without context for tool selection.

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