dld_search_rent_contracts

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

Annotations already declare the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds a genuine operational fact — it is a Tier 1 tool needing Dubai Pulse credentials — but says nothing about pagination, filtering behavior, or result volume.

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 short sentences with the resource and data source front-loaded; nothing is padded. It could arguably be one sentence, but there is no waste.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a search tool with geography and bedroom filters, the description omits any hint of scope breadth or how filters combine, leaving it only minimally adequate.

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 100%, so each parameter (area, limit, bedrooms) is already documented in the schema. The description adds no additional semantic detail beyond what the structured fields provide, which is the baseline-3 case.

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 (Search) and resource (DLD rent contracts / Ejari data) plus the data source (Dubai Pulse). This distinguishes it from dld_search_transactions, though the description never names that sibling explicitly to make the boundary airtight.

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 offers only a prerequisite ('requires Dubai Pulse credentials'), not usage guidance. It never says when to choose this over dld_search_transactions, rent_estimate, or ejari_guide, nor when not to use it.

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