List StreetEasy search areas and return the full area hierarchy from its public location picker. Use the resulting area IDs to run rental searches.
List StreetEasy search areas. Returns the complete area hierarchy exposed by StreetEasy's public homepage location picker. Use area IDs with streeteasy-rentals-search.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool 'Returns the complete area hierarchy,' indicating a read-only enumeration with a bounded output, which is helpful. It does not mention caching, rate limits, or the exact response shape, leaving a modest gap for a null-annotation tool.
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?
Two tight sentences, front-loaded with the core action followed by scope and the intended downstream consumer. No filler; every sentence adds information.
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 lookup with no output schema and no annotations, the description adequately characterizes both the operation and its return value ('complete area hierarchy'). An agent has enough to call it correctly and knows how to use the result, with only minor detail about the response format 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?
The tool takes zero parameters (empty schema, 100% coverage), so there are no parameter semantics to document and the baseline for a no-param tool applies. Nothing in the description is needed to clarify inputs.
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?
States a specific verb+resource ('List StreetEasy search areas') and clarifies scope as the 'complete area hierarchy exposed by StreetEasy's public homepage location picker.' This is a distinct reference/lookup tool within the streeteasy_* family, though it doesn't explicitly contrast itself against siblings like streeteasy_quick_search or the market_data 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 sentence 'Use area IDs with streeteasy-rentals-search' signals downstream consumption and hints at the workflow, which is genuinely useful. However, there is no explicit when/when-not guidance or statement of prerequisites, so the usage is only implied rather than fully specified.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.