getRealtimeLocationByAnum

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

No annotations are provided, so the description carries full burden. It describes the core behavior (retrieving realtime location) but doesn't disclose important traits like whether this is a read-only operation, potential rate limits, authentication requirements, or what happens when aircraft number is invalid. The description adds basic context but lacks comprehensive behavioral disclosure.

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?

Two sentences with zero waste. First sentence states purpose, second provides crucial usage guidance. Every word earns its place, and the most important information (purpose) is 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?

For a single-parameter read operation with no output schema, the description provides good context about purpose and usage guidelines. However, without annotations or output schema, it could better explain what the return value contains (e.g., coordinates, altitude, timestamp) and any limitations. The completeness is strong but not perfect given the lack of structured metadata.

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 100%, so the schema already documents the parameter type and format. The description adds minor clarification about the format ('Aircraft registration number like B2021, B2022, B2023, etc.') but doesn't provide additional semantic context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Get') and resource ('flight realtime location') with specific qualification ('by aircraft number'). It distinguishes from siblings by focusing on realtime location retrieval rather than search, transfer info, or weather 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?

Explicitly provides when-not-to-use guidance: 'if aircraft number is unknown, you should try to request it using searchFlightsByNumber tool.' This names a specific alternative tool for the prerequisite step, giving clear context for tool selection.

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