opnsense_dns_add_override

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

No annotations provided, and description omits side effects (e.g., overwrites existing record? requires permissions?), leaving behavioral traits unclear for a write operation.

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 concise, front-loaded sentences with no redundant information, efficiently conveying purpose and necessary follow-up action.

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 the add-and-apply workflow, but lacks error behavior and idempotency details; for a simple creation tool without output schema, it is adequate but not fully complete.

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?

All parameters already described in schema (100% coverage); description adds no extra meaning beyond restating record types already in enum.

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 'Add a DNS host override (A/AAAA/CNAME record) to Unbound' with specific verb and resource, distinguishing it from siblings like add_forward and block_domain.

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?

It mentions the follow-up step 'Run opnsense_dns_apply afterwards to activate,' which is helpful, but lacks when-to-use versus alternatives or exclusions.

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