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

Annotations already declare destructiveHint=true, but the description adds concrete consequences not encoded there: monitoring of the server stops and the action is irreversible. It stops short of saying what happens to dependent monitors or status-page entries.

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?

Two short sentences, zero filler, with the destructive warning front-loaded right after the action. Nothing repeats the name or title verbatim.

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?

Adequate for a one-parameter destructive tool whose annotations and schema already cover safety and input. The only gap is downstream effects (attached monitors, status pages), which an agent might want before committing an irreversible action.

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% for the single required "id" parameter, so the schema carries full weight. The description adds no detail on id format or whether the server must be stopped first; 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?

Specific verb+resource ("Delete a server") with an added effect ("stop watching it") that clarifies what deletion means operationally. It does not name a sibling such as vs_servers_update or vs_status_page_servers_remove, so the agent gets no explicit routing help.

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 caution "This cannot be undone" implies careful use, but there is no explicit when-to-use vs when-not guidance and no pointer to alternatives (e.g. vs_servers_update to modify, vs_monitors_delete for monitor removal). Usage is only inferable from the verb.

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