fritz_set_smart_home_switch

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about side effects on a physical actuator, behavior on an unknown AIN, idempotency, or permissions. For a mutation tool with zero annotation coverage this is a significant gap beyond the name restatement.

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?

A single front-loaded sentence with no wasted words and the identifier convention up front. Its brevity leans toward under-specification rather than verbosity, but structurally it is efficient.

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?

A parameterized mutation tool with no annotations, no output schema, and 0% schema description coverage needs far more: expected return, error behavior, and what 'on' does. Only the AIN hint is supplied, leaving most of what an agent needs missing.

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 compensate; it only clarifies that 'ain' is a device identifier. The 'on' parameter is never mentioned, and despite the boolean type the description does not confirm whether it sets an explicit state versus performing a toggle.

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+resource ("Switch a smart-home actuator") and identifies the key input ("by its AIN"), which is enough to distinguish it from read-only siblings like fritz_smart_home_devices. The verb "switch" is however ambiguous between toggling and setting an explicit state, which the description never resolves.

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?

No indication of when to use this versus fritz_smart_home_devices or fritz_get_device, and no mention that the AIN must first be obtained from the device listing. Prerequisites and alternatives are left entirely to inference.

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