dld_lookup_broker

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

No annotations are provided, so the description must fully disclose behavior. It only states the basic lookup functionality without explaining search semantics, result format, pagination, or any side effects. The description lacks sufficient detail for an agent to understand the tool's behavior beyond a generic lookup.

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 consists of two concise, front-loaded sentences with no wasted words. The first sentence states the core purpose, and the second provides essential prerequisites.

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?

While the description covers the core purpose and prerequisites, it lacks behavioral details such as how the search works (e.g., exact vs. substring matching), how the limit parameter affects results, and what the output schema contains. With an output schema present, some return value details are covered, but the description could be more complete for agent decision-making.

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 parameters (name, limit, license_number) are already well-documented in the schema. The description adds no additional meaning or context beyond the schema, so a baseline score of 3 is appropriate.

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 the action 'Look up' and the subject 'RERA-registered Dubai brokers', distinguishing it from all sibling tools, none of which are broker lookups.

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 provides context on when to use the tool (for Dubai broker lookups) and prerequisites ('Tier 1 tool, requires Dubai Pulse credentials'), but does not explicitly state when not to use it or list alternatives.

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