Gross rental yield for residential property in a Dubai area: median annual rent per m2, median sale price per m2, and gross yield %, from official DLD sale + rental (Ejari) data.
| Name | Required | Description | Default |
|---|---|---|---|
| area | Yes | Area name in English. | |
| property_type | No | 'Flat' (default) or 'Villa'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description mentions data source (DLD and Ejari) implying reliability but does not disclose read-only nature, rate limits, error cases, or update frequency. Basic transparency for a read operation.
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?
Single sentence, 27 words, front-loaded with purpose and outputs. No extraneous 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?
No output schema, but description explains return values. Missing details on error handling (invalid area) and default behavior for property_type. Data source is included. Adequate for a simple query tool.
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 coverage is 100%, baseline 3. Description adds context about area being in Dubai and outputs (rent, sale price, yield) beyond the schema descriptions. Property_type default is mentioned in schema, description reinforces residential focus.
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?
Description clearly states the tool computes gross rental yield for a Dubai residential area, specifying the exact outputs (median rent per m2, median sale price per m2, yield %) and data source. It distinguishes from siblings by focusing specifically on yield calculation.
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?
No guidance on when to use this tool versus siblings like area_snapshot, market_overview, or rank_areas_by_yield. The description does not mention prerequisites or context for choosing this tool.
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.
Each tool has a clearly distinct purpose: listing areas, getting area snapshot, comparing areas, market overview, affordability calculation, yield ranking, and rental yield. No overlap or ambiguity.
All tool names follow a consistent pattern of lowercase snake_case with verbs like 'list', 'compare', 'rank', 'get' (implied in area_snapshot). Very predictable.
Seven tools are well-scoped for a Dubai real estate data server. Each tool adds distinct value without redundancy, fitting the ideal range of 3-15.
The set covers essential operations: listing areas, detailed snapshots, comparisons, market overview, affordability filtering, and yield analysis. No obvious gaps for the domain.