SimBrief 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. It discloses that the output is 'raw JSON' and specifies exclusions (navlog, notams, alternate navlog), which adds useful behavioral context. However, it doesn't mention potential errors (e.g., if plan_id is invalid), performance aspects like rate limits, or authentication needs, leaving gaps for a tool that fetches data.

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 front-loaded with the core purpose in the first sentence, followed by usage context and parameter guidance in two additional concise sentences. Every sentence adds value without redundancy, making it efficient and well-structured.

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), no annotations, and low schema coverage, the description does a good job by explaining the tool's purpose, usage, and parameter semantics. However, it could be more complete by addressing potential error cases or linking to sibling tools for excluded sections, keeping it from a perfect score.

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 'plan_id': it explains that leaving it empty retrieves the latest dispatch, which clarifies its optional nature and default behavior. Since schema description coverage is 0% and there's only one parameter, this compensates well, though it doesn't detail the format or constraints of plan_id beyond being nullable.

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 a 'complete flight plan as raw JSON' with specific exclusions (navlog, notams, alternate navlog), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_flight_summary' or 'get_atc_flightplan', which might offer overlapping or alternative flight plan data, so it doesn't reach the highest score.

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 clear context for when to use this tool: for 'deep analysis or accessing fields not covered by the other tools', which implies it's more comprehensive than alternatives. It also specifies to 'Leave plan_id empty to get the latest dispatch', offering practical guidance. However, it doesn't explicitly name when not to use it or list specific alternatives among the many sibling tools, so it's not a perfect 5.

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