SimBrief MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool returns an 'ATC flight plan string ready for filing', implying a read-only operation, but doesn't specify data sources, permissions required, error conditions, or whether it's cached/real-time. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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—two sentences with zero waste. The first sentence front-loads the core purpose and key components, and the second provides essential parameter guidance. Every word earns its place without redundancy.

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 the tool has an output schema (which handles return values), low complexity (one optional parameter), and no annotations, the description is reasonably complete. It covers the purpose, key output components, and parameter semantics, though it could benefit from more behavioral context like error handling or data freshness.

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 description adds meaningful context for the single parameter: it explains that leaving 'plan_id' empty retrieves the latest dispatch, which clarifies the default behavior not evident from the schema alone. With 0% schema description coverage and only one parameter, this adequately compensates, though it doesn't detail format or constraints of 'plan_id'.

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 tool retrieves an ATC flight plan string with specific components (route, callsign, flight type, flight rules, equipment codes), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_full_flight_plan' or 'get_flight_summary', which likely provide different aspects of flight planning data.

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 implied usage guidance by mentioning to 'leave plan_id empty to get the latest dispatch', which suggests when to omit the parameter. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_full_flight_plan' or other siblings, nor does it mention prerequisites or exclusions.

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