Read Multiple SimVars

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds genuinely useful behavioral context beyond annotations: results are keyed by 'NAME' or 'NAME:index', and a failed variable does not abort the batch but carries an 'error' entry. This helps the agent anticipate partial failures.

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?

Two short sentences with no filler: the first states the core action, the second provides the critical failure/result behavior. The most important information is front-loaded and every sentence earns its place.

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 one-parameter schema, rich schema descriptions, and output schema, the description plus structured data fully support correct invocation. The partial-failure and keying behavior are explicitly covered. Missing only an explicit routing note about when to prefer this over the single-read sibling, which is not essential.

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?

Schema description coverage is 100%, with detailed documentation of the 'variables' parameter including accepted keys, an example, and a max of 100 entries. The tool description adds no additional parameter meaning, so the baseline of 3 applies.

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 a specific verb, resource, and batching intent: 'Read several SimVars in one call.' It is clearly distinguishable from the singular msfs_get_simvar tool by the plural and batching wording, though it does not explicitly name or contrast that sibling.

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 batching language implies it should be used when multiple SimVars are needed in one call, but there is no explicit when-to-use guidance, no mention of when not to use it, and no alternative tool names. The agent must infer the choice between this and msfs_get_simvar.

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