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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is covered. The description adds genuine extra context beyond that: the removal is immediate ("at once") and the owner's DNS record is deliberately left in place rather than cleaned up. The one gap is that it doesn't say whether the caller needs ownership of the node or app.

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 tight sentences with zero filler; the primary effect is front-loaded and the DNS caveat follows. Nothing needs trimming.

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 three-param destructive tool with no output schema, the description plus annotations cover effect, timing, and side effects. Authorization requirements and any error cases (e.g., domain not currently assigned) are the only missing pieces.

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 description coverage is 100%, so all three parameters (host, node_id, service_name) are already documented, including the cross-reference to nerdit_list_nodes. The description adds no parameter-level detail beyond the schema, 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?

States a specific verb and resource — stop serving an app at a domain — and adds the effect of freeing a slot, which implies a quota. It is clearly the inverse of the sibling nerdit_add_domain, though it doesn't name that sibling explicitly.

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 explains what happens but gives no when-to-use guidance, no prerequisites (e.g., the domain must currently be assigned), and no reference to alternatives such as nerdit_list_domains or nerdit_check_domain. The agent must infer usage from context alone.

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