CHAP: the home's address at home

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the safety profile is covered externally. The description adds genuine context beyond them: what the address is for (phones/dashboards unchanged after a switch) and that address=null stops the moving behavior. It does not state reversibility of a previously set address or any auth prerequisites, leaving that to the annotations.

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 tightly written sentences with the core action front-loaded and no filler. The second sentence on the null case earns its place, but the phrasing 'follows whichever install runs the home' is slightly indirect jargon that costs a little 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 mutation tool with annotations but no output schema, the definition covers purpose, effect, and null semantics adequately. It stops short of explaining prerequisites (e.g. needing instance_id from vomehome_list_instances) or what a caller observes after the change, which a destructive configuration call could usefully include.

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 coverage is 100%, so baseline is 3. The description goes beyond the schema's terse 'An address on the house network, or null.' by supplying a concrete CIDR example (192.168.1.15/24) and clarifying the functional meaning of null ('stops moving it'), which the schema does not convey.

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 (Set) and resource (the house-network address / home address), and the follow-up clause explains the intent ('follows whichever install runs the home'). It distinguishes itself conceptually from the other vomehome_chap_* siblings, though it never names them explicitly.

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 explains what happens after the call but gives no when-to-use guidance relative to alternatives such as vomehome_chap_switch, vomehome_chap_link_standby, or vomehome_use_instance. The agent must infer that this is the configuration step for a stable home address.

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