dld_search_transactions

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

No annotations are provided, so the description carries full burden. It discloses that credentials are required and that a structured error occurs if they are missing. However, it does not mention rate limits, pagination behavior, data freshness, or what happens when no results are found. More behavioral context is needed.

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 short and front-loaded with the main purpose. It uses two sentences effectively, with the first defining the tool and the second providing prerequisites. It is concise without 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?

Given that there is an output schema (context indicates it exists), the description does not need to detail return values. The description is minimal but sufficient for basic understanding. However, it could mention that the tool returns a list of transactions or specify the data source format.

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?

The input schema already covers all parameters with descriptions (100% coverage). The description does not add any additional meaning beyond what is in the schema, such as value ranges or examples. Therefore, it is adequate but not additive.

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 states 'Search Dubai Land Department real estate sale transactions.' It specifies the action (search), resource (real estate sale transactions), and domain (Dubai Land Department). However, it does not explicitly differentiate from the sibling tool 'dld_search_rent_contracts', though the distinction is implied by the word 'sale'.

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 description mentions that it is a 'Tier 1 tool' and requires 'Dubai Pulse credentials', including specific environment variables. It warns about a structured error if credentials are missing. However, it does not provide explicit guidance on when to use this tool versus alternatives like dld_search_rent_contracts or other DLD tools.

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