repl_install_package

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful behavior beyond annotations: the package is importable in all sessions immediately and uses pip or uv if available. That is meaningful behavioral context for a simple install tool.

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 three sentences plus a minimal Args/Returns structure, all front-loaded and free of filler. Every sentence adds value, and the structure is clean.

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 simple, but the parameter mismatch is a critical gap. The description does not explain the actual input wrapper, and while an output schema exists, the description's wrong parameter documentation makes the tool incomplete and error-prone to invoke.

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 description says 'Args: params: Package specifier', but the input schema requires 'params' to be an object containing a nested 'package' field. This is misleading and would cause an agent to pass the package string directly as {'params': 'pandas'} instead of {'params': {'package': 'pandas'}}, leading to validation failures.

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 'Install a Python package using pip (or uv if available)', which is a specific verb+resource. It distinguishes this tool from sibling tools that manage code execution, files, and namespace variables.

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 context: 'The package becomes importable in all sessions immediately', which conveys when to use it. It does not explicitly mention alternatives or exclusions, but the purpose is unambiguous, earning a 4.

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