query_dld

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

Without annotations, the description carries the burden of transparency. It states it returns data but does not explicitly declare read-only behavior, auth requirements, or side effects. As a query tool, it is implied to be non-destructive, but explicit mention would improve transparency.

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 well-structured with clear sections for Args, Returns, and Examples. Every sentence adds value, and the examples are concise yet informative. No unnecessary repetition.

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 no output schema, the description adequately explains return formats for each metric type. It covers all parameters and provides examples. Minor gap: does not specify behavior when incompatible parameters (e.g., rentals with property_type) are used.

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?

With 0% schema coverage, the description fully explains all 8 parameters, including defaults, allowed values (e.g., 'sales' or 'rentals'), and constraints (e.g., 'property_type' only for sales). Examples demonstrate usage effectively.

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 'Query Dubai property data - sales transactions or rental contracts', specifying the verb, resource, and the two data types. This is precise and distinguishes any potential confusion between sales and rentals.

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 includes usage examples and explains when to use each parameter, such as 'property_type' being for sales only. However, it lacks explicit guidance on when not to use the tool or alternatives, but since no sibling tools exist, it remains clear enough.

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