run_pip_install

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

No annotations are provided, so the description carries the full disclosure burden. It does not state whether this mutates the application environment, whether it is long-running or blocking, how failures (missing requirements.txt, pip errors) surface, or whether it is idempotent — all material for an install operation.

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?

A single, front-loaded sentence with no filler or redundancy. It is appropriately sized for the amount of information delivered, though that economy comes at the cost of the missing behavioral detail scored elsewhere.

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 mutating, potentially slow and failure-prone install operation with no annotations and no output schema, the definition says nothing about prerequisites, side effects, expected duration, or what a result or error looks like. The full schema reduces the parameter gap but not the operational gap.

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% and there is only one parameter, app_name, already described as the 'Registered Python application name'. The description adds nothing beyond that, so the baseline 3 applies.

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 names a specific action (run pip dependency installation) and a specific target (a registered Python application), which is much clearer than a bare 'run_pip_install'. It does not, however, distinguish itself from nearby siblings such as run_npm_install, setup_python_app, or ensure_passenger_deps, so the agent must infer the boundary.

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 when-to-use guidance, no stated prerequisites (e.g. that the app must first be created via setup_python_app and appear in list_python_apps), and no mention of alternatives for Node-based or Passenger-based dependency installs. The single word 'registered' hints at a precondition but never spells it out.

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