router_toggle_ipv6

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

With no annotations, the description carries the full burden. It usefully discloses that a 'Network Guard safety check' exists and that force bypasses it, which is real behavioral context. But it never says whether toggling drops the cellular connection, whether the setting survives reboot, or what the safety check verifies — gaps that matter for a mutation tool.

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?

Three short, front-loaded sentences: an action summary, a usage recommendation, then arg docs. No filler, though the enable arg line mostly restates the obvious from the first sentence.

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?

An output schema exists, so return values are covered. For an unannotated mutation tool, however, the description should address disruption to the connection and persistence of the setting, neither of which it does.

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 document both params, and it does: enable (True enable / False disable) and force (bypass Network Guard safety check). The meaning of force is explained beyond its bare name, though the consequences of bypassing the guard remain unstated.

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?

States a specific verb pair (enables/disables) against a specific resource and scope (the IPv6 stack on the cellular connection). No sibling touches IPv6, and the cellular-connection qualifier keeps it from being confused with general Wi-Fi or DNS tools.

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?

Gives a concrete condition for using the disable path: 'Disabling IPv6 is recommended if Hutch IPv6 routing is introducing dual-stack timeout delays.' It does not state when not to use the tool (e.g., when IPv6 is required by the carrier), so it stops short of full routing guidance.

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