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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds data-source context ('published on the register') but does not disclose additional behavioral traits such as rate limits, pagination specifics, or data freshness. With annotations carrying the behavioral burden, a 3 is appropriate.

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?

The description is a single well-structured sentence that front-loads the core purpose and then lists the returned fields. There is no redundant wording or repeated schema 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?

There is no output schema, so the description's enumeration of returned fields (broker number/name, licence dates, office, phone) partly compensates. Combined with the rich input schema and safety annotations, the tool is sufficiently complete for an agent to call it correctly. It could further mention default sorting or pagination limits, but those are already in the schema.

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 every parameter is already documented in the input schema. The description does not add parameter-specific semantics beyond what the schema provides, but it doesn't need to; baseline 3 is warranted.

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 clearly identifies the resource ('licensed real-estate brokers on the Dubai Land Department register') and enumerates the specific data returned: broker number/name, licence dates, brokerage office, and office phone. This distinguishes it from sibling tools like dld_list_developers and dld_list_areas.

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?

No explicit guidance is given about when to use this tool versus the sibling list/search tools. The description implies it is for broker registry data, but it does not state when to prefer this over dld_search_transactions, dld_search_buildings, or dld_list_developers, nor does it mention any exclusions or prerequisites.

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