ipython_install_deps

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

No annotations are present, so the description carries full burden. It discloses that the operation writes to the interpreter's site-packages and requires network access, and it specifies the mechanism (using that interpreter's own python -m pip). This makes the mutating nature and prerequisites clear, though it does not discuss idempotency or failure modes.

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?

Three sentences, each with a distinct job: state the action and target, give the trigger condition, and list side effects/prerequisites. No redundant phrasing.

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 two-parameter install tool with no output schema, the description covers purpose, trigger, side effects, and a prerequisite (network). It could mention idempotency or failure output, but nothing an agent needs to invoke it correctly is missing.

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%, so the schema already documents both parameters. The description adds context that python_path's own pip is used, clarifying that the installation targets that interpreter's environment. It does not add detail on timeout_ms, but the schema covers its meaning.

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?

States a specific verb ('Install'), the exact packages (IPython, ipykernel, jupyter_client), and the target environment (Python 2.7 interpreter). This differentiates it from siblings like ipython_start and ipython_status, which run or check rather than install.

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?

Explicitly tells the agent when to call it: when ipython_start reports missing dependencies. It also implies the alternative is to run ipython_start once deps are present, giving a clear trigger condition.

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