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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond them: this returns published catalog data only, with no live availability and no confirmed prices, which tells the agent how stale/authoritative the results are. It stops short of describing result fields or ordering, but the data-freshness caveat is the important disclosure.

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 compact sentence-fragment with no filler: the resource scope comes first and the data-quality caveat follows immediately. Every clause carries information an agent needs.

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 no-parameter, no-output-schema list tool, the description establishes what is enumerated and the limits of that data. The main remaining gap is that nothing describes what attributes each listed car type carries, which an agent must know to decide whether this tool answers its question.

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?

The tool takes zero parameters, so there is nothing in the input schema for the description to clarify. Baseline for a parameterless tool applies, and the description correctly avoids inventing filter semantics the schema does not support.

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 names a specific resource (published private car and limousine types in Vietnam), which the verb in the tool name 'list' turns into a clear list operation. It implicitly separates itself from the sibling list_charter_coaches by scoping to private cars and limousines, though it never names that sibling explicitly.

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 clause 'no live availability or confirmed prices' functions as a when-not-to-use signal, steering agents away from this tool for pricing or booking checks. However, it never names the alternative (e.g., get_quote_instructions) or states the positive condition under which this tool is the right choice, leaving the routing inference to the agent.

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