npm_delete_proxy_host

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

No annotations are provided, so the description must fully disclose behavior. It only states the action but does not reveal whether deletion is permanent, whether it fails if the host is in use, any side effects on related resources (streams, redirections), or required permissions. This is a significant gap for a destructive 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?

The description is a single sentence, 'Delete a proxy host by id,' with every word contributing meaning. It is highly concise and front-loaded, with no wasted text or irrelevant details.

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?

The description lacks essential context for a destructive tool with no output schema or annotations. It doesn't state what happens on success (e.g., return value), whether the operation is reversible, or any preconditions. For a simple one-parameter delete, it misses the opportunity to clarify expected outcomes and edge cases.

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 schema has one parameter 'id' with no description (0% coverage). The tool description only says 'by id', which adds minimal meaning (that id is the proxy host identifier) but does not explain the expected format, how to obtain it, or any constraints beyond the schema's integer/exclusiveMinimum. The description does not compensate for the lack of schema documentation.

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 'Delete a proxy host by id' uses a specific verb (delete) and resource (proxy host), clearly distinguishing it from sibling tools like create, update, enable, disable, or get. It is immediately obvious what the tool does.

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 gives no explicit guidance on when to use delete versus alternatives such as disable (which might be a non-destructive option) or the broader context of proxy host lifecycle. It implies usage through the verb but doesn't mention exclusions or alternatives.

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