npm_delete_redirection_host

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

No annotations are provided, so the description carries the full burden. It says 'Delete' but discloses nothing about whether the operation is irreversible, what related resources (certificates, forwarding rules) are affected, or what authorization is required for a destructive mutation.

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?

One short sentence, front-loaded with the verb and resource, with no filler. It is efficient, though terse enough that it leaves room for necessary behavioral detail it never supplies.

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 an irreversible delete with no annotations and no output schema, the description omits the safety information an agent needs: confirmation expectations, side effects on dependent resources, and error cases for invalid IDs. The parameter is covered, but the destructive semantics are not.

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% and the single parameter is fully documented in the schema as 'The ID of the redirection host to delete'. The description's 'by ID' adds nothing beyond it, 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?

The description states a specific verb ('Delete') and resource ('redirection host'), and the resource name alone separates it from the many sibling deletes (npm_delete_dead_host, npm_delete_proxy_host, npm_delete_stream, npm_delete_certificate). It does not explicitly reference siblings, but the scope is unambiguous.

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 delete versus when to disable (npm_disable_redirection_host) or update, and no prerequisites, permissions, or warnings about irreversibility are stated. The agent must infer everything about usage context.

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