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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It does add two useful traits: results are 'citable' and results carry ids that can be passed to fetch. It says nothing about result volume, ranking, or what happens on a miss, so the added value is modest.

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 sentences, front-loaded with the resource and scope, then the follow-up mechanism. Nothing is wasted, though 'Dubai Diligence' is named twice and the middle list of covered content is dense.

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 no explanation, and the single required parameter is fully documented in the schema. The description covers scope, output nature (citable), and the id-to-fetch path. The remaining gap is the lack of disambiguation against the many overlapping Dubai-specific siblings.

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?

There is a single parameter with 100% schema description coverage, including worked examples ('Dubai Marina prices'). The description adds no further semantics for 'query' such as phrasing, language, or supported operators, so the baseline of 3 applies.

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 a specific resource (the Dubai Land Department record published by Dubai Diligence), and enumerates the covered content: communities/districts with prices, rents, yields, plus the Index. That is far clearer than the bare name 'search'. It stops short of distinguishing itself from the specialized siblings like dubai_community_prices or dubai_house_price_index, which cover overlapping data.

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 closing clause 'pass an id to fetch for the full text' gives one concrete routing rule to the fetch sibling, which is genuinely useful. However, there is no guidance on when to use this general search versus the seven domain-specific Dubai tools, so an agent facing a price or yield question has no basis for choosing.

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