Register an additional OneHome session at runtime

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

Discloses registration of a new transport, marking active, and that previous sessions stay. Explains routing using MLS suffixes. Annotations indicate destructiveHint=true, which aligns with state modification. Description adds security notes about magic links in chat history, beyond 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?

The description is comprehensive and well-structured, with clear sections. It front-loads the purpose and input shapes. Slightly long but every sentence adds value; could be tightened slightly but not excessively verbose.

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?

Fully covers input types, detection, session management, routing, response contents (session_id, active_session_id, auth mode, etc.), and security. No output schema, but response structure is described. Completes the agent's understanding.

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?

Single 'input' parameter with schema description. The description greatly expands on valid input formats (URL with token, JWT, email-token) and the detection logic. Provides examples and explains how each is processed.

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 it registers an additional authenticated session using various credential types. It differentiates from sibling tools like onehome_set_active_session by explaining session management and routing with MLS suffixes.

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?

Explicitly explains when to use: when a buyer holds shares across multiple agents/MLSes. Details input shape detection (URL, JWT, email-token) and mentions alternatives for session switching by name. Provides clear context on usage.

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