deleteVhost

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

The description is extremely terse. While 'Delete' implies destructive action, it does not disclose any behavioral traits such as irreversibility, required permissions, or impact on related resources. With no annotations, the description carries the full burden, which it fails to satisfy.

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, compact sentence that conveys the essential action. It is efficiently front-loaded and contains no wasted words, meeting the conciseness standard despite being minimal.

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 operation with no annotations, this description is insufficiently complete. It fails to mention consequences, approval requirements, or any side effects, and the output schema does not alleviate the need for such context.

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 documents a single parameter `vhost_id` (integer), and the description adds no additional meaning. Since the parameter is self-explanatory from its name and type, the lack of description is not a significant gap, but the tool still provides no extra semantic support.

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 resource ('vhost/endpoint'), distinguishing it from sibling tools like createVhost, getVhost, and listVhosts. It is specific, unambiguous, and uses a strong verb.

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, nor any prerequisites or exclusions. The tool name and sibling list imply its use case, but the description does not explicitly clarify when it should be invoked.

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