python_install

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

No annotations are provided, so the description carries full responsibility for disclosure. It reveals that installation occurs but does not mention side effects, permissions, download behavior, or impact on the current environment. For a mutating operation, this is a significant transparency gap.

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 is front-loaded and appropriate for a simple install command.

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 minimal behavioral disclosure, the one-parameter schema is fully covered and an output schema exists, so the description need not explain return values. The phrase 'managed Python version' gives enough context for this use case, though more detail on side effects would improve completeness.

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 coverage is 100% for the single 'version' parameter, which is already described as 'Python version request.' The description adds 'managed' but does not clarify version format, accepted values, or default behavior, so it adds minimal value beyond the schema.

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 clear verb ('Install') and specific resource ('managed Python version'), making the tool's primary function obvious. It is distinct enough from sibling tools like python_upgrade or tool_install, though it does not explicitly contrast them.

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 when a managed Python version is needed, but it provides no explicit guidance on when to prefer this tool over alternatives such as python_upgrade or python_pin. There is no stated context or exclusion criteria.

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