Connect to MSFS

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

Beyond the annotations, the description discloses an important side effect: it automatically attempts to load the MobiFlight WASM extension for L-var support. It also clarifies the ordering requirement. It does not describe failure behavior or the effect of calling it when already connected, but the idempotentHint annotation covers re-invocation safety.

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 two short sentences with no filler. The primary action is front-loaded, and the prerequisite and automatic WASM behavior each earn their place. This is concise without losing necessary guidance.

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 zero-parameter connection tool with an output schema and informative annotations, the description provides the essential invocation context: it must precede all other tools and it automatically handles WASM loading. No additional parameter or return-value detail is needed.

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 tool has zero parameters and a fully covered schema, so there is no parameter information that the description needs to add. The baseline of 4 applies because the invocation surface is fully described by the empty schema.

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 uses a specific verb and resource, 'Establish SimConnect connection to MSFS,' which clearly identifies the operation. It is further differentiated from siblings like msfs_disconnect and msfs_get_connection_status by its explicit connect action and the stated prerequisite that it must be called before any other tool.

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 explicitly states when to use it: 'Must be called before using any other tools.' This gives clear context for invocation. It does not explicitly name alternatives or exclusion cases, but siblings such as msfs_disconnect are obvious, and the strong prerequisite guidance is sufficient.

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