data_dubai_entities

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

With no annotations, the description should carry the burden. It states client-side filtering and no credentials, but doesn't disclose other behavioral traits like read-only nature or performance considerations. Adequate but not exceptional.

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?

Two sentences, concise and front-loaded with key information. Every sentence adds value.

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 the output schema and parameter schema, the description provides sufficient context for a simple listing tool. It mentions no credentials and client-side filtering.

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 covers parameter fully (100% coverage), but description adds that filtering is client-side, which is useful context beyond the schema's substring match description.

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?

Description clearly states the tool lists issuing entities, gives specific examples (RTA, DEWA, Dubai Police), and distinguishes from sibling tools like data_dubai_search and data_dubai_themes.

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?

Description mentions optional filtering and no credentials needed, implying it's for simple listing without server-side filtering. It doesn't explicitly state when not to use, but context is clear.

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