Fetch a OneHome saved search by id

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

Annotations already cover read-only, idempotent, and open-world behavior, so the description adds value by disclosing the session-context default for saved_search_id and the conditional suppression of listing_ids. This is meaningful behavioral context beyond what the annotations express, though it does not discuss edge cases like not-found behavior or authentication requirements.

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 compact and front-loaded with the core action and resource. Every sentence adds distinct value: identity, return shape, parameter behavior, variant differentiation, and defaulting behavior. No filler or redundant restatement of the title is present.

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 two-optional-parameter read-only fetch with no output schema, the description covers the essential return fields, both parameters, the session-context default, and the tool's canonical position among variants. An agent has enough information to select and invoke the tool correctly without additional context.

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 description coverage is 0%, so the description carries full weight for both parameters. It explains that saved_search_id is a UUID and defaults to session context when omitted, and that include_listing_ids: false suppresses the listing-id array for metadata-only callers. This fully compensates for the bare schema.

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 opens with a specific verb and resource ('Fetch the agent-curated saved search by its id'), and immediately distinguishes this tool from related variants by noting it is the canonical consumer-readable endpoint and that the by-groupId variant is agent-only. It also clearly enumerates the returned data, so an agent can predict what this tool produces without ambiguity.

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 gives clear usage context: it identifies this as the canonical consumer-readable endpoint, notes the agent-only by-groupId variant, and tells the agent to pass include_listing_ids: false when only metadata is needed. It does not explicitly route around the closely named sibling onehome_get_saved_search_with_listings, but the parameter guidance and endpoint classification are strong enough for most routing decisions.

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