estimate_fare

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

With no annotations, the description carries the full burden. It discloses that the tool calculates and presents an estimated fare, and the phrase 'before calling create_booking()' implies this tool does not itself create a booking. However, it does not detail return structure or potential side effects, leaving some ambiguity.

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 two sentences, front-loaded with the action ('Calculate...'), and every word adds value. It succinctly captures the inputs, output, and workflow without redundancy.

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?

The description is adequate for a fare estimation tool: it covers purpose, key inputs, output (fare in INR), and workflow. However, it lacks explicit return value fields or error conditions, which would be helpful given there is no output schema.

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 input schema has 100% description coverage for all 5 parameters, so the schema already documents each parameter. The description adds only 'INR' and 'distance' as output context, which does not significantly enhance parameter understanding beyond the schema.

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 clearly states the tool calculates distance and estimated fare in INR based on specific inputs, which is a distinct function among the sibling tools. It also explicitly references create_booking(), differentiating it as a pre-booking estimation step.

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 provides clear workflow guidance by instructing to present the fare to the guest for confirmation before calling create_booking(). It does not explicitly mention alternatives or when not to use it, but the integration with create_booking() establishes a clear usage context.

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