opn_list_dnsmasq_ranges

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

With no annotations, the description carries full burden. It notes that both IPv4 and IPv6 ranges appear in same list, lists key fields, and describes return format (dict with 'rows' and 'rowCount'). However, it omits pagination behavior (limit parameter) and search filtering details, leaving some ambiguity.

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?

Description is about 80 words in two paragraphs. Purpose is front-loaded, and key details follow. Some redundancy ('both DHCPv4 and DHCPv6' appears twice) but overall efficient and scannable.

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 simplicity and presence of an output schema, the description covers the output structure, key fields, and prerequisite. However, missing parameter explanations slightly reduce completeness. Still adequate for a list tool with existing output schema.

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%, so the description must explain parameters. It only mentions 'search' and 'limit' but does not describe their semantics (e.g., what search filters, how limit controls pagination). The listed key fields are for the output, not the input parameters.

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 'List dnsmasq DHCP ranges (both DHCPv4 and DHCPv6 with RA config).' Verb 'list' and resource 'dnsmasq DHCP ranges' are explicit, and the description distinguishes from sibling tools like opn_list_dhcp_leases by specifying ranges (pools) versus leases.

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 clear context: 'Use this to see configured DHCP address pools and Router Advertisement settings for each interface.' Also mentions prerequisite ('Requires the dnsmasq DNS/DHCP server'). Does not explicitly state when not to use or name alternative tools, but the context is sufficient for an agent.

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