Fetch a OneHome saved search by id

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint. The description adds value by detailing the returned fields (name, filters, polygon, listing count, listing_ids), the effect of the 'include_listing_ids' parameter, and the session-context default for saved_search_id. This goes beyond the 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 extremely concise with 3-4 sentences, all relevant and front-loaded. There is no redundant information; every sentence adds value: main action, return fields, parameter usage, and endpoint context.

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?

Despite no output schema, the description sufficiently lists the returned fields. It covers both optional parameters and their effects. It could be more complete by mentioning error behavior or the exact shape of nested objects like 'filters' and 'polygon', but for a simple read tool this is quite comprehensive.

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 0% schema description coverage, the description fully explains both parameters: 'include_listing_ids' (suppress listing-id array to get only metadata) and 'saved_search_id' (defaults to MCP's session context). This is excellent compensation for the lack of schema documentation.

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 uses the verb 'Fetch' and specifies the resource as 'agent-curated saved search by its id'. It distinguishes from the sibling 'onehome_get_saved_search_with_listings' by noting that this is the 'canonical consumer-readable endpoint' and the by-groupId variant is agent-only, though it could be more explicit about the difference between these tools.

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 provides guidance on when to use this tool (consumer-readable) vs. the agent-only variant (by-groupId). It also explains the optional parameter 'include_listing_ids' and the default behavior for 'saved_search_id'. It would benefit from explicitly stating when not to use this tool or when to use the sibling.

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