OlaChill Vietnam — Travel and Private Transport

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description usefully reinforces this by stating no booking is created. However, it says nothing about what the tool actually returns (text instructions? links? forms?) or any follow-up action required to complete a quote request.

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 front-loaded sentence with no filler, sized appropriately for a zero-argument helper tool. It could be marginally sharper by naming the return type, but every word earns its place.

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 no parameters and no output schema, the description carries the burden of explaining what an agent gets back and what to do next, and it omits both. It conveys the intent (get quote-request guidance without booking) but leaves the agent guessing about the response content.

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 for the description to clarify beyond the schema; baseline 4 applies. The description correctly does not waste words on non-existent inputs.

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 says the tool covers 'how to request a verified ... quote', which implies it returns instructional content rather than data, but it never states that explicitly (e.g. 'returns step-by-step instructions'). It is distinguishable in spirit from the listing siblings list_charter_coaches and list_private_cars, but the differentiation is only implied, not stated.

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 phrase 'without creating a booking' implies the context in which to use it (quote-only enquiries), but there is no explicit when-to-use, when-not-to-use, or pointer to the sibling listing tools. An agent must infer the routing decision.

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

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: this returns static published class listings and guidance, deliberately excluding live availability and confirmed prices, which tells the agent what answers it cannot get here. Return shape and any pagination are not described, keeping it below 5.

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 no filler, and the resource scope is front-loaded ahead of the data limitations. It is a fragment rather than a verb-led statement, which slightly weakens immediate readability.

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 zero-parameter read-only listing tool with no output schema, the agent needs to know what data is present and what is absent, and the description supplies exactly that. A brief note on the fields returned would make it fully self-sufficient.

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?

There are zero input parameters, so the baseline is 4. The description introduces no parameter concepts, and none are needed for a no-argument listing tool.

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 set — published Vietnam charter coach classes plus passenger/luggage guidance — which is clearly distinct from the sibling tools get_quote_instructions and list_private_cars. The verb is only implied (it reads as a noun phrase, 'Published ... classes'), so it stops short of the 5 mark, but no agent would confuse it with a quote or private-car tool.

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 availability or confirmed prices' gives a useful when-not-to-use boundary that implicitly pushes availability/pricing questions toward get_quote_instructions. However, the sibling is never named explicitly, and there is no positive statement of when this tool is the right choice versus alternatives.

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

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.