Fetch a saved search and inflate its listings in one call

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

Discloses internal operations (two internal calls), default values (group_id, saved_search_id from session context, sort default), and limitations (no PublicRemarks). No contradiction with 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?

Concise at ~150 words, front-loaded with the key purpose. Each sentence provides essential information without redundancy.

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?

Covers purpose, usage, behavior, return structure, and limitations. Lacks details on pagination behavior or error handling, but overall adequate given the tools complexity.

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?

Adds meaning for group_id, saved_search_id (defaults), and sort_field (default). But other parameters like page_num, page_size, sort_order, include_dislikes are not described beyond the schema. Schema coverage is low (14%), so more detail would be better.

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 combines fetching a saved search and inflating listings into one call. It distinguishes from sibling tools like onehome_get_saved_search and onehome_search_properties by explicitly mentioning the two-call sequence it replaces.

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?

Provides explicit guidance on when to use this tool instead of the two-call alternative. Also warns that PublicRemarks are missing and advises using onehome_get_property for full descriptions.

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