dld_search_transactions

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, and the description adds genuinely new context: the Dubai Pulse credential requirement and that a structured error is returned when the client ID/secret are unset. It stops short of describing result volume or pagination behavior for a limit-capped list tool.

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?

Front-loaded with the purpose in the first sentence, followed by two short operational facts; nothing is redundant or padded. 'Tier 1 tool' is internal catalogue jargon with unclear value to an invoking agent, a minor blemish on otherwise tight prose.

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?

An output schema exists so return values need not be described, and the description covers the auth-failure mode. For a three-param read-only search this is nearly complete; only the behavior when all filters are omitted or how limits interact with result volume is left unstated.

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 area, limit and property_type are already documented with defaults and ranges in the schema. The description contributes no additional meaning about these parameters, which is the expected baseline when the schema carries the load.

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 (Search) and resource (Dubai Land Department real estate sale transactions), which implicitly distinguishes it from the sibling dld_search_rent_contracts by scoping to sale rather than rent. It does not name that sibling explicitly, so the differentiation must be inferred from the noun.

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 when-to-use or when-not-to-use guidance and no named alternatives, though the specific 'sale transactions' scope implies the use case versus the rent-contract sibling. The credential prerequisite is stated but is an operational requirement rather than usage routing.

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