fritz_set_backhaul_steering

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

With no annotations, the description carries the full disclosure burden and provides almost none: it does not say whether enabling backhaul steering can momentarily drop mesh links, whether the change is reversible, whether it requires a mesh topology, or what happens on non-mesh setups. Only the bare toggle semantics are conveyed.

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, the core action front-loaded and the sibling disambiguation second. No filler or redundancy.

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 one-boolean toggle with no output schema this is borderline adequate, but without annotations the description should have covered network-disruption effects and prerequisites; that omission leaves real gaps for a mutation on mesh infrastructure.

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%, but the single parameter is a self-evident boolean named 'enabled' and the description's 'on or off' phrasing maps directly onto it. No additional meaning (defaults, failure behavior) is added beyond the 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?

The description pairs a specific verb (turn on/off) with a specific resource (mesh backhaul steering), so the operation is unambiguous. It also distinguishes itself from a nearby sibling by noting it is separate from client band steering, though it never names fritz_set_band_steering directly.

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 line 'This is separate from client band steering' implies which sibling handles the other case, but gives no explicit condition for choosing this tool, no prerequisites (e.g., mesh master role), and no when-not guidance.

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