Aviationstack MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('get random airplanes') without explaining how it behaves: whether it returns live data or static information, what format the output takes, if there are rate limits, or what 'detailed info' includes. This leaves significant gaps in understanding the tool's operation.

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 extremely concise with just one sentence: 'MCP tool to get random airplanes.' It's front-loaded and wastes no words, though this brevity comes at the cost of completeness. Every word serves a purpose in stating the basic function.

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?

Given that there's an output schema (which should document return values), the description doesn't need to explain output details. However, with no annotations, 1 parameter with 0% schema coverage, and sibling tools present, the description is incomplete. It covers the basic purpose but lacks usage context, parameter explanation, and behavioral details needed for effective tool selection.

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 description coverage is 0%, meaning the input schema provides no descriptions for parameters. The tool description mentions 'random airplanes' but doesn't explain the 'number_of_airplanes' parameter at all. It fails to add meaning beyond the bare schema, leaving the parameter's purpose and constraints undocumented.

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 states the tool 'get random airplanes' which provides a basic verb+resource combination. However, it lacks specificity about what 'detailed info' entails and doesn't differentiate from sibling tools like 'random_aircraft_type' or 'random_cities_detailed_info' beyond the resource type. The purpose is clear but vague regarding the nature of the information returned.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'random_aircraft_type' (which might provide different data) or 'flights_with_airline' (which deals with actual flights rather than airplane details). There's no context about use cases or exclusions.

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