Delete redirection host

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

The description does not disclose that deletion is permanent and irreversible, nor does it mention any side effects or required permissions. With no annotations, the description carries the full burden of behavioral disclosure, which it fails to meet.

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 extremely brief but lacks necessary details, making it under-specified rather than concise. It uses only 4 words, omitting critical information.

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 delete tool with no output schema, no parameter descriptions, and no annotations, the description is incomplete. It should at minimum clarify the permanent nature of the operation and the role of the id parameter.

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?

The description adds no value beyond the schema for the parameter 'id.' With schema description coverage at 0%, the description should explain that the 'id' identifies the redirection host to delete, but it does not.

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 'Delete a redirection host,' which is a specific verb+resource combination. It accurately reflects the tool's function but does not distinguish from related operations like disabling, which could be added for clarity.

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?

No guidance is provided on when to use this tool versus alternatives such as npm_disable_redirection_host. The description lacks any context about appropriate usage scenarios or prerequisites.

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