List all registered Zillow sessions

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

Adds substantial context beyond annotations: describes the empty/null degenerate case, clarifies that the registry doesn't affect which account requests use, and explains the ContextMint Bridge tab-sign-in requirement for switching accounts.

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?

Front-loaded with the core purpose and return shape, then adds the important caveat about label-only semantics. Somewhat long, but every sentence earns its place given the unusual registry-vs-account distinction.

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?

No output schema, so description carries the return-value burden, which it does by naming sessions and active_session_id. It covers the key behavioral gotcha, though a hint about how the label maps to account changes via zillow_set_active_session would close the loop.

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?

Zero parameters, so baseline is 4. No params to document, and the description correctly omits parameter discussion.

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?

State a specific verb (List) and resource (registered Zillow sessions/account labels) and names the exact return fields (sessions, active_session_id), distinguishing it from the sibling zillow_set_active_session and zillow_register_session.

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 the registry is a label only and that switching accounts requires signing a tab into the desired account, effectively routing agents toward the correct behavior. However, it doesn't explicitly name zillow_set_active_session as the alternative for changing the active session.

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