delete_network

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

The description clearly discloses that the tool does NOT delete anything, returns guidance, and that no direct network deletion API exists. This goes well beyond the readOnlyHint annotation and gives the agent accurate expectations for invoking the tool.

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 short, front-loaded with the critical caveat that nothing is deleted, and followed by a minimal Args section. Every sentence contributes useful information with no filler.

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 one-parameter advisory tool with readOnlyHint and an output schema, the description covers the surprising behavior, the platform deletion rule, and the argument. The only minor gap is not explaining where the network_id comes from, but this is a small omission given the schema already identifies the required argument.

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 0%, but the description only restates the parameter as 'network_id: Network ID,' which adds little beyond the schema's title 'Network Id.' It does not explain how to obtain the ID, what format it should be, or any validation behavior, so it fails to compensate for the missing schema descriptions.

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 states it is an 'Advisory helper for network deletion' and explicitly says 'This tool does NOT delete anything — it returns guidance.' This corrects the potentially misleading delete_network name and clearly distinguishes it from actual deletion tools like delete_service.

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 the platform behavior: EasyPanel automatically removes a network once all services in it are deleted, and there is no direct API to delete a network. This makes the helper's purpose clear. It could be stronger by explicitly naming delete_service as the alternative for deleting services first.

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