npm_delete_dead_host

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

With no annotations provided, the description is the sole disclosure of behavior. It states the action (delete) but omits any consequences such as irreversibility, required permissions, or cascading effects. For a destructive tool, this is minimal transparency.

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?

The description is a single, concise sentence that immediately conveys the action, target, and method. Every word is essential, and it is properly front-loaded.

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 delete operation with one parameter, the description covers the core purpose. However, gaps remain: no indication of what happens on success or failure, no prerequisites, and no warning about permanence. It is adequate but lacks behavioral context that would be helpful for an agent.

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 0%, so the description must clarify the parameter. Saying 'by id' confirms the role of the 'id' parameter but does not explain how to obtain the id (e.g., from a list operation) or any additional meaning beyond the schema's integer type.

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 clearly states the action ('Delete') and the specific resource ('404 (dead) host') and identifies how the host is referenced ('by id'). This distinguishes it from sibling delete tools like npm_delete_proxy_host or npm_delete_redirection_host by specifying the exact target type.

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 description implies use for deleting dead hosts, but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions. The reader must infer usage from the tool name and description alone.

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