Flights to the powder

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description need not reiterate safety. It adds context about outputting flight-search links (not bookings), but this is already implied by annotations. No contradiction with annotations.

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?

Description is concise and efficient, front-loaded with the primary action, followed by funnel positioning and parameter breakdown. No redundant sentences.

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?

Covers all essential aspects: main functionality, relationship to siblings, parameter guidance, and output type. Good annotations and output schema further reduce ambiguity.

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 coverage is 100%, so baseline is 3. Description repeats parameter details from schema with minor additions (e.g., 'use search_resorts to resolve a name'), offering marginal extra value over 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?

Description clearly states the tool finds gateway airports from a resort and returns flight-search links, positioning it as the 'get there' leg. It distinguishes from siblings like find_best_powder and book_lodging by specifying its role in the trip funnel.

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?

Explicitly states when to use: after finding powder, before booking lodging. It names siblings (find_best_powder, find_powder_trips, book_lodging) and advises using search_resorts to resolve resort names, providing clear context for agent decision-making.

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