restart_python_app

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the mechanism (Passenger restart trigger) and implies an in-place, quick restart, but says nothing about expected downtime, permission requirements, or the failure mode when the app is not registered or not running.

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 the action, target, and mechanism in order; no filler or redundant restatement of the tool name.

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 simple two-parameter, low-risk operation with full schema coverage and no output schema, this is nearly sufficient. The remaining gap is operational context — what success looks like and what happens if the app is absent — which keeps it from a 5.

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%, so both parameters are already documented, and the description adds no meaning beyond them — it does not clarify the interplay between optional app_name and required app_root or the expected path format. Baseline 3 applies since the schema does the work.

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 pairs a specific verb ("Restart") with a specific resource ("a running Python WSGI application") and even names the mechanism (Passenger restart trigger). That framing separates it cleanly from siblings like setup_python_app, destroy_python_app, and restart_nodejs_app.

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?

Usage is implied by "a running ... application" — the app must already exist and be running — but no explicit when-to-use/when-not guidance is given, nor any pointer to setup_python_app for apps that are not yet registered. The agent must infer prerequisites.

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