fr24_search

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

No annotations exist, so the description carries the full behavioral burden, and it does disclose one genuinely useful trait: the endpoint is unauthenticated. It says nothing about rate limits, quotas, result freshness, or whether the data is live versus cached, which are material for an unauthed FR24 endpoint.

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?

A single compact sentence with no filler and the key qualifier (unauthed) front-loaded. It is terse almost to a fault, but nothing in it is wasted.

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 search tool with a single undocumented parameter and no annotations, the description should explain query format and route the agent away from near-duplicate siblings. An output schema exists, so return values need not be covered, but the input side is left substantially ambiguous.

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 0%: the single parameter is named only 'q' with no title or description. The description implies q accepts an aircraft, airport, or flight identifier, which is some compensation, but it gives no format, examples, or matching rules (callsign vs registration vs ICAO code).

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?

States a specific verb (search) and resource (FlightRadar24 data) with the entity scope spelled out: aircraft, airports, flights. That is clear on its own, but it does nothing to distinguish itself from aviation siblings like query_aircraft, lookup_aircraft, or the adsb_by_* family.

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?

There is no when-to-use guidance and no mention of alternatives, even though the sibling list contains several overlapping aviation lookups. The agent must guess whether to reach for this or query_aircraft/lookup_aircraft/adsb_by_callsign.

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