python_upgrade

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

With no annotations, the description alone must disclose behavioral traits. 'Reinstall' implies a potentially destructive action, but the description does not state whether it requires an internet connection, whether it replaces the existing version, or whether it affects virtual environments. It only states the action without any safety or side-effect information.

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 that gets straight to the point. It does not waste words, although it could include more useful context; this dimension rewards the efficient structure.

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 reinstall operation with no annotations, the description lacks critical context such as whether the operation is destructive, whether it can be reverted, or how the 'version' parameter is interpreted (e.g., exact version vs. range). The existence of an output schema reduces the need to explain return values, but the behavioral gaps remain.

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 provides a description for the 'version' parameter ('Python version request.'), and the schema coverage is 100%. The tool description adds no additional semantics beyond the schema, so the baseline of 3 is appropriate.

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 the verb 'reinstall' and identifies the resource as 'a managed Python version', which is specific and actionable. However, the tool name is 'python_upgrade' while the description says 'reinstall' rather than 'upgrade', creating ambiguity about whether this tool upgrades the version or simply reinstalls the same one. This ambiguity prevents a higher score.

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?

There is no guidance on when to use this tool instead of siblings like python_install, python_uninstall, or python_find. The description gives no context for selecting this tool, nor does it mention any prerequisites or alternatives.

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