compare_free_zones

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds only that results come back ranked, without explaining the ranking basis, scoring criteria, or what happens when filters eliminate every zone.

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?

A single tight sentence with the output form front-loaded. Nothing redundant, nothing wasted.

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?

With a full output schema, rich annotations and 100% parameter coverage, the description only needs to convey intent and it does. The one gap is that the ranking logic driving the shortlist is unexplained.

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 schema already defines limit, sector, budget_aed, visa_count and needs_physical_office. The description adds no meaning beyond the schema – notably nothing about how budget or visa_count influence the ranking.

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?

States a specific verb (compare) and resource (Dubai free zones) plus the output shape (ranked shortlist), which distinguishes it from list_free_zones and free_zone_details by implication. It never names those siblings explicitly, so the differentiation is left for the agent to infer.

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?

"For a specific use case" hints that this is the decision-support tool versus the raw listing tools, but no when/when-not condition or alternative is spelled out. An agent must guess that list_free_zones/free_zone_details are the non-comparison paths.

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