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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the critical clarification 'No booking is created by this tool,' reinforcing its non-destructive and read-only nature beyond what annotations state. It doesn't elaborate on rate limits or authentication, but given the strong annotation coverage, the added context is sufficient for a 4.

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 a single, efficient sentence that front-loads the primary action and includes the key disclaimer about not creating a booking. There is no redundant information, and every phrase adds value: the purpose, the filled-in details, the end-user benefit, and the non-booking clarification. This is exemplary conciseness.

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 14 parameters and no output schema, the description should clarify what the tool returns (a URL string) and any special behavior. It states it 'builds a link' but does not explicitly describe the return format or how the agent should handle the link. It also omits error handling or validation notes, though all parameters are optional. Given the tool's moderate complexity and lack of output schema, the description leaves some gaps for an agent to infer.

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 50% description coverage, meaning many parameters lack explanations. The description lists the main categories (date, time, passengers, luggage, pickup, drop-off, contact details), which helps identify which parameters are relevant but does not add specific format, constraints, or relationships between parameters beyond what the schema already provides. It provides a high-level overview but doesn't fully compensate for the parameters without schema descriptions.

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 verb 'Build' and the resource 'link to Tripyana's online booking form' with specific details to fill in (date, time, passengers, luggage, pickup, drop-off, contact details). It distinguishes itself from booking-creation tools by explicitly noting 'No booking is created by this tool,' making its purpose unambiguous and distinct from siblings like pricing tools.

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 usage when a pre-filled booking link is needed for a traveller to complete the booking, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or competing tools. There is no direct guidance on when not to use it or what alternatives exist, so while the context is implied, explicit usage direction is missing.

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