opn_delete_dnsmasq_range

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

Discloses immediate application and automatic reconfiguration. With no annotations, description carries full burden; however, it lacks details on irreversibility, permissions, or error handling.

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?

Three concise sentences, each serving a purpose: action, immediacy, prerequisite and return type. No redundancy.

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?

Covers key aspects: what it does, how to prepare (list prerequisite), immediate effect, and return value. For a simple one-param delete, it is sufficient; missing error behavior.

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 has 0% description coverage; description compensates by explaining UUID parameter's role (identifier for the range). Could include format hint like 'UUID string'.

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?

Clearly states verb 'Delete', resource 'dnsmasq DHCP range', and method 'by UUID'. Distinguishes from siblings like opn_add_dnsmasq_range and opn_update_dnsmasq_range.

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?

Provides explicit prerequisite: 'Use opn_list_dnsmasq_ranges first to find the UUID.' Mentions immediate application. Does not mention when-not-to-use or alternative tools, but context is clear.

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