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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the data provenance (Ejari rent contracts against registered sale prices) and the guardrail that a minimum sales volume prevents thin markets from topping the list. It omits sort direction, whether results are capped by market coverage, and any auth or rate-limit notes, keeping it short of a 5.

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 tightly written sentences, front-loaded with the tool's identity and then the methodology/guardrail. Nothing is redundant and 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?

For a two-parameter, no-output-schema ranking tool, the description covers purpose, computation, and the rationale for the key filter. It lacks detail on return fields or sort order, but those gaps are minor and largely inferable from 'ranked by'.

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%, so the baseline is 3, but the description adds genuine meaning for min_sales_12m by explaining its purpose ('so a thin market cannot top the list'), which is more than the schema's bare definition. The limit parameter receives no additional context.

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 names a specific output (Dubai communities ranked by gross rental yield) and the methodology behind it (registered Ejari rent contracts vs. registered sale prices), which clearly separates it from siblings like dubai_community_prices or dubai_price_split. It stops short of explicitly naming the alternative tools, but the resource and verb 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?

There is no statement of when to choose this tool over dubai_community_prices or dubai_compare_areas, and no prerequisites or exclusions are given. The ranking intent is implied only by the phrase 'ranked by gross rental yield'.

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