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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: the data source (Dubai Land Department open data), daily refresh cadence, CC BY 4.0 license, and that each response includes the source page URL. It stops short of describing pagination or latency, but the provenance and freshness disclosure is genuinely useful.

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, no filler. The first front-loads exactly what comes back; the second carries provenance, freshness, license, and attribution URL. Every clause earns its place.

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 carries the job of telling the agent what it will receive, and it enumerates the return fields (sales count, median price, YoY changes, off-plan share, breakdowns, yearly history, monthly series) plus the source URL. For a zero-parameter read tool, nothing an agent needs to call it correctly is missing.

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 are zero parameters, so the baseline is 4. The description correctly adds no parameter semantics because there are none to explain; the detail it does give is about output content rather than inputs.

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 (Get) and resource (overall Dubai property market summary) and then enumerates the exact metrics returned. It reads as a distinct aggregate-snapshot tool, separable from siblings like get_monthly_report and list_rankings.

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 phrase 'overall Dubai property market summary' implies usage, but the description never says when to pick this over get_monthly_report or list_rankings, nor names any prerequisites or exclusions. Usage is implied rather than stated.

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