fritz_lan_dhcp

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

No annotations exist, so the description carries the full burden. It never states that this is a read-only operation, whether it requires a session/auth, whether the `host` argument changes the target device, or what an unconfigured DHCP server returns. Only the implied read-only nature can be inferred from the noun list.

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 short sentences with no filler, and the sibling redirect is front-loaded right after the scope statement. The opening is a noun fragment rather than a verb clause, which costs a bit of clarity.

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 read tool with one optional parameter this is close to adequate – it hints at the three returned fields. But with no annotation, no output schema, and an undocumented `host` parameter, the definition leaves real gaps about targeting and return shape.

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% and the single `host` parameter is completely unexplained in both schema and description. An agent cannot tell whether `host` is a router address, a subnet, or a filter, nor whether omitting it (default null) targets the local device.

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 names the specific resource (LAN DHCP configuration) and the fields it exposes (range, mask, DNS), which is enough to distinguish it from siblings like fritz_wifi_networks or fritz_list_devices. The verb is only implied (it reads as a retrieval), so it falls short of a fully explicit 'get the DHCP settings'.

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 explicitly routes the reservation use case elsewhere: 'Per-device reservations use fritz_reserve_ipv4.' That is a concrete when-not plus a named alternative. It never states the positive trigger ('use this to inspect the DHCP pool'), so it is slightly one-sided.

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