opnsense_dns_infra

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

No annotations are provided, so the description must fully disclose behavioral traits. It says 'dump' implying a read operation but does not explicitly confirm non-destructiveness, permissions needed, or side effects. The output format and whether it might return large data are also not addressed.

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 sentences with no wasted words. The first sentence states what the tool does, the second explains when to use it. Information is front-loaded and easy to scan.

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 simple parameterless diagnostic tool, the description covers purpose and use case well. It lacks behavioral transparency details, but given no output schema and low complexity, it is largely adequate. Could mention read-only nature.

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?

With zero parameters and 100% schema coverage (trivially), the description adds meaning beyond the schema by clarifying the tool targets the Unbound infrastructure cache and lists specific attributes. This compensates for the abstract tool name.

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?

Description clearly states it dumps the Unbound infrastructure cache and lists specific data (RTT, EDNS support, lame delegation). The verb 'dump' combined with the resource 'Unbound infrastructure cache' is specific and distinguishes it from sibling DNS tools like opnsense_dns_stats or opnsense_dns_cache_search.

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?

Ends with 'Useful for diagnosing upstream DNS connectivity issues,' providing a usage context. However, it does not explicitly state when to use this tool versus alternatives like opnsense_dns_diagnostics or opnsense_dns_cache_search, nor does it mention when not to use it.

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