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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false輩 the description adds a critical behavioral nuance: coverage is limited to the current calendar year. This complements the annotations without contradicting them, though it doesn't describe pagination or rate-limit behavior.

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?

Three terse sentences front-load the core purpose, then the two critical constraints (coverage year and required date range). Every sentence contributes essential selection or invocation information with no wasted words.

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?

The description covers what the tool returns, its data source, and its limitations; the schema covers all parameter semantics with examples. With no output schema, the listing of return fields partially compensates. For an 11-param tool, an explicit note about sorting or pagination would help, but the schema examples already show those details.

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 100%, so the schema already documents all 11 parameters and enum meanings. The description only reinforces that the date range is required and doesn't add new semantics. A baseline 3 is appropriate given the schema fully carries the parameter 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 names the specific resource (Dubai Land Department property transactions), enumerates the transaction types (sales, mortgages, gifts), and lists the returned attributes (value, procedure, area/district, project, property type, room count, nearest metro/mall/landmark). This clearly distinguishes it from sibling tools like dld_search_rents, dld_search_valuations, and dld_search_buildings.

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?

It explicitly states that a date range is required and warns that earlier years come back empty, which tells an agent when the tool is not suitable. It stops short of recommending an alternative sibling or providing explicit when-not-to-use reasoning beyond the year limitation, so not a full 5.

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