restart_nodejs_app

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

With no annotations, the description carries the full burden, and it does disclose the mechanism (updating the Passenger restart trigger) and that the effect is 'instantly'. However, it omits whether the restart causes brief downtime, whether it is safe/idempotent, what happens if the app is not running, and any authentication or permission requirements.

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 and the mechanism, no redundant restatement of the name or schema fields. Nothing to trim.

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 2-parameter mutation tool with no output schema and no annotations, the definition covers what it does and how, but leaves gaps on prerequisites, failure behavior, and downtime impact that an agent would want before invoking a restart on a live application.

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 app_name and app_root are already documented in the schema, including the example format for app_root. The description adds no additional meaning about which identifier takes precedence or how app_name and app_root interact when both are supplied, 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?

States a specific verb ('Restart') and resource ('a running Node.js application') and even names the underlying mechanism (Passenger restart trigger). An agent can distinguish it from siblings like setup_nodejs_app or destroy_nodejs_app, though it never explicitly contrasts with restart_python_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?

The phrase 'a running' implies the app must already exist, but there is no explicit when-to-use guidance, no prerequisites (registered app, Passenger enabled), and no mention of alternatives such as disable/enable_passenger_app or redeploy_from_github when a full redeploy is needed.

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