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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds valuable context beyond this: 'No login, no browser, no proxies' and a per-call cost. It also references robots.txt and sitemap usage in the emirate parameter, giving insight into compliance and technical approach, though it does not describe failure modes or return formats.

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: the first covers the core function and filters; the second covers logistics (no login, cost). No filler, front-loaded with the most relevant action. Every clause adds 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?

For a tool with five optional parameters and no output schema, the description provides a complete high-level picture: what data is fetched, the source, sorting, and operational constraints. The parameter descriptions flesh out the details. It does not describe the response structure, but that is often acceptable when listing rows are predictable and no output schema exists.

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% and each parameter has a detailed description with enums and constraints. The main description adds no new parameter semantics beyond naming deal type and emirate, which is already covered. Baseline 3 is appropriate since the schema carries the burden.

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 uses specific verbs and resources: 'Pull live apartment, villa, penthouse and townhouse listings straight from PropertyFinder.ae', and identifies the portal as the UAE's biggest real-estate portal. It clearly distinguishes from sibling real-estate tools by geographic scope and portal, avoiding any ambiguity.

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 implies usage for UAE real-estate listings but does not explicitly state when to use this tool over alternatives, nor does it exclude other tools. It lacks explicit 'when to use' or 'when not to use' guidance that would rank higher.

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