Get the signed-in user's saved homes on homes.com

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

Beyond the readOnlyHint and idempotentHint annotations, the description reveals that the tool scrapes the favorites page, that field values are best-effort DOM extractions that may be missing, and what missing values mean. It also specifies the exact error condition for unauthenticated sessions.

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 dense but every sentence earns its place: purpose, source, return shape, auth requirement, data-quality caveats, and cross-reference to a sibling. Key operational constraints are front-loaded.

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 zero-parameter, read-only tool with no output schema, the description fully equips the agent: what it returns, what may be missing, what errors to expect, and how to get canonical records. Nothing essential is left out.

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?

With zero parameters, the schema leaves no parameter semantics to clarify; the baseline is 4. The description still adds useful context about implicit inputs: the signed-in user's session and browser tab.

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 states a specific verb and resource: retrieving the signed-in user's saved homes from homes.com's /customer/dashboard/favorites/. It clearly distinguishes itself from the sibling saved_searches tool and references homes_get_property as a complementary tool for canonical records.

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?

It explicitly states the user must be signed in, warns that the call throws SessionNotAuthenticatedError otherwise, and advises when to switch to homes_get_property per row for canonical data. This gives the agent concrete conditions for correct use versus alternatives.

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