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

With no annotations, the description supplies some behavioral context: it is FREE, returns only solutions/advice (route, price, why, ETA), and is fast (<1 min). It does not state whether the tool mutates anything, requires auth, or has limits/fallbacks, so it does not fully carry the burden.

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?

One compact sentence, front-loaded with the cost signal (FREE), then the core behavior and output elements. Every clause earns its place; no filler.

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 single-parameter intake tool with no output schema, the description names the input format and the main return elements (route, price, why, ETA). It falls just short of complete because it doesn't state boundaries (e.g., that it doesn't execute the route/booking) or how ambiguous requests are handled.

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 schema has one required string `want` with 0% description coverage. The description compensates by specifying that `want` is free text representing the user's need, which is the key semantic info an agent needs; there are no enums or nested constraints to document.

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 the tool is a free-form intake/front door that turns a natural-language want into concrete solutions with route/price/why/ETA. It clearly distinguishes its role from the specialized sibling tools by calling itself the 'front door,' though it does not name an alternative 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?

'Concierge front door' and 'say what you need in free text' establish when to use it: as a starting point for unspecified or unstructured requests. It does not mention explicit exclusions or name which specialized sibling to prefer for a given need, so it stops short of a 5.

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