Switch which registered OneHome session is active

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

Annotations already indicate destructiveHint=true (mutation) and idempotentHint=true. The description adds context by explaining the consequential effect on subsequent requests. It does not contradict annotations and adequately describes the behavior.

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?

The description is four sentences, tightly written with no extraneous information. It is front-loaded with the core purpose and sequentially provides usage context, parameter guidance, and consequence.

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?

Given the tool's simplicity (one parameter, no output schema), the description fully covers what the tool does, when to use it, where to get the parameter, and the effect on subsequent behavior. No gaps remain.

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% (one parameter with a description). The description adds value by explaining the parameter's source (previous calls to onehome_set_auth or onehome_get_session_context) and its purpose, slightly exceeding the schema's description.

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 clearly states the tool's purpose: 'Force a specific registered session to be the active one.' It specifies the verb 'force' and the resource 'registered session,' and distinguishes it from sibling tools by focusing on session management, while siblings are largely data retrieval 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?

The description explicitly states when to use the tool: 'Useful when MLS-suffix routing picks the wrong session.' It provides concrete scenarios and references parent tools for obtaining the session_id. It also clarifies the effect on subsequent requests without a ~MLS suffix.

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