Get Flight Details

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

Adds behavioral context beyond annotations: 'All timestamps are UTC', 'Returns a single flight object, or null if not found', and explains that flight_number returns most recent instance. No contradiction with annotations (readOnlyHint=true is consistent).

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?

Four sentences, each serving a purpose: purpose, parameter constraint, behavior with alternative, return format. No redundant language. Well-structured and front-loaded.

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 essential aspects: single result, null handling, UTC timestamps, parameter usage. Without an output schema, it mentions 'single flight object' but omits field details. Sufficient for low-complexity tool with good sibling differentiation.

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%, baseline 3. Description adds meaning by noting flight_id is internal UUID, flight_number is normalized, and enforces mutual exclusivity ('Provide exactly one of'), which is a constraint not present in 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?

Clearly states 'Get detailed information about a single specific flight', with verb 'Get' and resource 'flight'. Distinguishes from sibling flighty_search_flights by specifying single vs. multiple results and mentioning the alternative search tool.

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 instructs to provide exactly one of flight_id or flight_number, and directs to use flighty_search_flights when wanting all instances. Provides clear context but does not mention other siblings like flighty_get_flight_status for status-specific queries.

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