list_free_zones

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

Discloses it is a read-only list operation returning a compact list with specific fields. No annotations exist, so description carries full burden; it is clear and non-misleading.

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 concise sentences. First sentence states the core action and scope, second details the output structure. No extraneous text.

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?

For a parameterless list-all tool with an output schema, the description is sufficient. It covers purpose and output fields. Could mention absence of sorting/filtering but not necessary.

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?

No input parameters, so schema coverage is 100%. Description adds value by specifying the return fields (id, name, sector, location, initial license cost). Baseline 4 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?

Clearly states verb 'List' and resource 'every Dubai free zone in the curated dataset'. Differentiates from siblings like 'compare_free_zones' and 'free_zone_details' by emphasizing broad listing.

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?

Implied usage for getting a compact overview of all free zones, but no explicit when-to-use or when-not-to-use compared to alternatives like 'compare_free_zones' or 'free_zone_details'.

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