caddy_config_delete

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

The annotations already mark this as destructive, but the description adds valuable context: deleting a parent node removes all descendants, and the confirm flag must be explicitly set to true. This goes beyond the basic destructive hint and clarifies real-world behavior, making it highly transparent.

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 concise and front-loaded with the core action. The first sentence states the purpose, followed by necessary cascade and safety details. There is a slight redundancy between 'Delete config' and 'Removes the config node,' but overall it is efficient and well-structured.

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?

Given the tool's moderate complexity, the description fully covers the destructive nature, cascading behavior, and the required confirm flag. With schema covering both parameters and annotations providing safety hints, no critical information is missing. The description is complete for safe and correct usage.

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%, so the baseline is 3. The description adds extra meaning by explaining that deleting a path also deletes descendants, which affects how the 'path' parameter is interpreted. It reinforces the confirm requirement but doesn't add syntax details. This is a modest but meaningful addition.

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 tool's purpose with a specific verb ('Delete') and resource ('config at a JSON path'). It distinguishes from siblings like caddy_config_set and caddy_config_get by explicitly focusing on deletion. The cascading behavior example further clarifies the scope.

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 provides clear context on how to use the tool: 'Requires confirm=true' and explains the cascading deletion effect. While it doesn't explicitly mention when to prefer this over alternatives, the sibling context makes it obvious. No exclusions are given, but the guidance is sufficient for typical use.

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