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 what data is retrieved (METAR, TAF, ATIS) and the plan_id parameter behavior, but doesn't disclose important behavioral traits like whether this is a read-only operation, what permissions might be needed, rate limits, data freshness guarantees, or error conditions. For a tool with no annotation coverage, this leaves significant gaps.

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 two sentences that each earn their place. The first sentence establishes the core purpose and scope, while the second provides essential parameter guidance. There's zero wasted language or redundancy, making it efficiently front-loaded with critical information.

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), a single parameter with good semantic coverage in the description, and no complex nested structures, the description is reasonably complete for basic usage. However, as a weather data tool with no annotations, it should ideally mention data sources, update frequency, or limitations to provide better context for the agent.

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 about the single parameter (plan_id) that goes beyond the schema's 0% coverage. It explains that leaving plan_id empty retrieves 'the latest dispatch,' which provides crucial semantic understanding of how this parameter affects the tool's behavior. This significantly compensates for the lack of schema descriptions.

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 current weather information (METAR, TAF, ATIS) for specific airports (departure, arrival, alternate), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like get_notams (which might provide weather-related notices) or explain how this weather data differs from what other tools might provide.

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 some usage context by explaining when to leave plan_id empty ('to get the latest dispatch'), which implies an alternative usage pattern. However, it doesn't explicitly state when to use this tool versus alternatives like get_notams for weather-related notices or how it relates to other flight planning tools in the sibling list. The guidance is implied rather than explicit.

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