Keyword search across QUANTUM-tracked pinui-binui compounds by compound name, city, or neighborhood. Use when user asks about a specific compound or area.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | Optional Hebrew city name filter (e.g. "תל אביב", "רמת גן"). | |
| limit | No | ||
| query | Yes | Search query (Hebrew or English). Matched against compound name, city, neighborhood. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states the search scope and fields, but omits details on pagination, result limits, error behavior, or whether the search is fuzzy/exact. This is insufficient for an unannotated 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 concise sentences that front-load the purpose and provide usage guidance. No redundant or unnecessary words.
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?
The description covers purpose and usage but lacks behavioral details (pagination, sorting, error handling, output structure) that would help an agent use the tool reliably, especially given the absence of annotations and output schema.
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 67% (query and city have descriptions, limit does not). The tool description paraphrases the query parameter's matching fields but adds no new semantics for city or limit. It does not compensate for the missing limit description.
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 explicitly states the verb 'search', the resource 'QUANTUM-tracked pinui-binui compounds', and the search fields 'compound name, city, or neighborhood'. It distinguishes itself from sibling tools like get_compound_details by focusing on keyword-based lookup.
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 advises 'Use when user asks about a specific compound or area', providing clear context. However, it does not explicitly exclude cases where a compound ID is known or mention sibling tools like get_compound_details as alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct lookups: search, detail, methodology, plan status, registry, recent changes, and top-ranked opportunities. There is some overlap in statutory status returns between get_compound_details, urban_renewal_registry, and planning_status_by_plan, but their descriptions clarify the source and scope enough to avoid major confusion.
The naming mixes verb-led patterns like get_, list_, and search_ with noun-style names like planning_status_by_plan and urban_renewal_registry. It is still readable and mostly predictable, but the lack of a uniform verb_noun convention makes the pattern less consistent.
Seven tools is well-scoped for a domain-specific analyzer server. Each tool addresses a distinct user need, and the count feels neither thin nor bloated.
The surface covers core analysis workflows: searching, retrieving detailed compound data, checking official registry status, inspecting live plan status, seeing recent statutory changes, and finding top mispriced opportunities. Minor gaps exist—like a general list/filter tool or historical comparison—but agents can work around them.