opnsense_kea_apply

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

The description mentions 'reconfigure service', indicating a reload of the Kea service. However, it does not detail potential side effects (e.g., brief DHCP interruption) or note that the action is safe. With no annotations, more disclosure would improve transparency.

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 extremely concise: one sentence stating the action and a brief usage hint. No redundant words, easy to parse.

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 (no params, no output schema), the description covers the essential: what it does and when to use it. It could briefly mention the effect after applying (e.g., changes become active), but it is largely 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?

The tool has zero parameters and 100% schema coverage, so the description does not need to add parameter info. The baseline for zero parameters is 4, and the description adds no unnecessary parameter details.

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 verb 'Apply' and the resource 'pending Kea DHCP configuration changes', and provides context 'reconfigure service'. It distinguishes from sibling apply tools (e.g., opnsense_fw_apply) by specifying Kea DHCP.

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 explicitly advises 'Run after subnet or reservation changes', giving clear usage context. It does not explicitly list when not to use, but the guidance is sufficient given the tool's specific purpose.

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