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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description correctly spends its words elsewhere: it states the hard result cap of 10, the provenance of prices ('exactly as binayah.ae shows it'), and the caveat that list prices change and availability must be confirmed on the page. That last point is real behavioral guidance an agent cannot get from annotations.

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 what is searched, then what comes back, then the staleness caveat in the order an agent needs it. The word 'exactly as binayah.ae shows it' is slightly wordy but earns its place by flagging format fidelity.

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?

With no output schema, the description correctly enumerates return fields (developer, community, starting price, handover, unit types, project URL). The only material gap is that it never says what happens when the limit is reached or whether a zero-result response differs from a failure.

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 80%, so the schema already documents query, bedrooms, developer and max_price_aed. The description adds only the framing that budget and bedroom filters are optional and that only the starting price is compared against the budget, which largely restates the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource ('Search new and off-plan projects listed on binayah.ae') and enumerates the filterable dimensions (community, developer, name, budget, bedrooms). It does not explicitly contrast itself with the closest sibling, project_price_check, but the resource and scope are unambiguous.

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?

Usage is only implied — the closing instruction to 'send people to the page for current availability' hints at the discovery-then-verify workflow, but there is no explicit when-to-use-this vs. when-to-use-another-tool guidance. An agent must infer that project_price_check is the deeper-dive alternative.

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