destroy_python_app

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

No annotations are provided, so the description carries the full behavioral burden. It implies a destructive mutation via "remove," but says nothing about irreversibility, whether application files or virtualenvs are deleted, whether a running process is stopped, or what permissions are needed — all critical for a destroy 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 efficient, though the brevity comes at the cost of the behavioral detail a destructive tool warrants.

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 destructive, zero-annotation tool with no output schema, the description should explain consequences and preconditions. Instead it leaves the agent unaware of what is actually removed, whether the action is reversible, and what happens to the running 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% with a single required parameter (app_name), which the schema already documents as "Registered application name to remove." The description adds no format hints, case-sensitivity notes, or resolution rules beyond what the schema supplies, so the baseline of 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 uses specific verbs ("Unregister and remove") plus a clear resource ("Python application configuration"), which is enough to separate it from setup_python_app, restart_python_app, and destroy_nodejs_app. It stops short of explicitly naming those siblings or the distinction between unregistering and deleting files, so it is clear but not maximally differentiated.

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 guidance on when to use this versus setup_python_app or restart_python_app, and no stated preconditions (for example, whether the app must be stopped or disabled first). The agent must infer the usage context entirely from the tool name.

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