data_dubai_search

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

With no annotations, the description carries full burden. It discloses that no credentials are needed and that it returns metadata only. However, it omits behavioral traits like rate limits, pagination defaults, or whether the search is read-only. The mention of '600+ dataset descriptions' adds some context but is not exhaustive.

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 extremely concise, with two clear sentences plus a bolded note. It is front-loaded with the action and uses formatting to highlight the key constraint (METADATA ONLY). No 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 an output schema exists, the description does not need to explain return values. It covers the essential context: the portal replaced Dubai Pulse, the catalog size, and the credential requirement. However, for a tool with siblings, a brief note on how it differs (e.g., 'for searching dataset metadata, not for entities/themes') would improve completeness.

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 coverage is 100%, so the baseline is 3. The description does not add any additional meaning or context to the parameters beyond what is already in the input schema (page, query, page_size).

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 it searches the data.dubai catalog for dataset metadata. It specifies that it's metadata only and mentions the portal replacement (Dubai Pulse). However, it does not explicitly differentiate from sibling tools like data_dubai_entities or data_dubai_themes, which may have overlapping purposes.

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 about when to use (for catalog metadata) and when not to (for dataset APIs, which require credentials). However, it offers no guidance on choosing between this tool and its siblings (e.g., data_dubai_entities, data_dubai_themes), which could lead to confusion.

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