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

Annotations already indicate a safe read-only, idempotent operation. The description adds meaningful context by clarifying the result is 'Indicative' and 'Not a quote,' and discloses the scope of Jenesis's planning styles, which helps set expectations about the nature and applicability of the output.

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?

The description is three short, information-dense sentences. Every sentence earns its place by adding either a disclaimer ('Not a quote'), a scope definition, or the source of the estimate.

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?

Despite having five parameters and no output schema, the description does not explain the output format (e.g., total vs. per person, currency units beyond 'USD'), nor does it clarify the meaning of parameters like region or inclusions. The dataset implications are under-specified for a tool of this complexity.

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 0%, so the description must compensate, but it provides no direct explanation of any parameter. The phrase 'Mid-range to ultra-luxury' subtly maps to the style enum, yet nights, travelers, region, and the optional inclusions array remain completely unaddressed.

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 tool's intent is clear from the title and the description's reference to a budget calculator producing a USD range. It is distinct from sibling tools like list_journeys or start_enquiry, though the description itself doesn't explicitly name a verb like 'estimates' or 'calculates'.

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 description implies use for mid-range to ultra-luxury trip planning via 'Mid-range to ultra-luxury is what Jenesis plans,' and 'Not a quote' hints it shouldn't be used for binding quotes. However, no explicit when-to-use, when-not-to-use, or alternatives to sibling tools are provided.

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