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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one behavioral qualifier — that only 'active' markets are returned — which is useful, but says nothing about result size, ordering, pagination, or what 'representative' means in practice.

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 short sentence with no filler, and the core verb is front-loaded. It is arguably under-specified rather than verbose, which is a completeness problem rather than a structure problem.

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?

An output schema exists, so return values need not be explained, and there are no required parameters, keeping the call surface simple. However, with four sibling list_* tools, the description leaves the agent without the routing information it needs to pick this one correctly.

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% and both parameters (agent_source, agent_session_id) are documented in the schema as compatibility/attribution fields. The description adds no parameter meaning, so the baseline 3 applies.

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 gives a verb (List) and enumerates the taxonomy it returns (countries, airports, services, representative providers), but the resource name 'markets' is never defined and the enumeration overlaps with siblings list_destinations and list_providers. An agent cannot confidently tell whether 'representative providers' means this tool returns providers or just a sample of them, so sibling differentiation is missing.

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?

There is no statement of when to use this tool versus list_destinations, list_providers, or list_rental_vehicles, and no prerequisites or exclusions. The single sentence is purely descriptive; the agent must infer routing from the name alone.

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