list_simvars

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

With no annotations, the description bears full responsibility. It clarifies that the tool searches a 'catalog' (likely a static reference) rather than live simulator values, and lists categories for filtering. However, it does not disclose pagination, limits, or whether results are case-sensitive, leaving some behavioral ambiguity.

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 and a bullet list. Every sentence adds value. The core action and optional filters are front-loaded, with categories listed separately for clarity. No waste.

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's simplicity (2 optional params, no required params) and the presence of an output schema (not shown but exists), the description is complete enough. It covers the search functionality, default behavior, and categories. No additional context is needed for correct selection or invocation.

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 coverage is 0% (no parameter descriptions). The description adds meaning by explaining that 'query' is a keyword and 'category' selects from the listed categories. It provides a specific list of categories, which is valuable beyond the schema's empty defaults. However, it does not detail valid formats or case sensitivity.

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: 'Search the SimVar catalog by keyword and/or category.' It specifies the action (search), resource (SimVar catalog), and scope (by keyword/category). The additional note 'Empty args list everything' clarifies default behavior. This distinguishes it from siblings like get_simvar (single var) and get_simvars (multiple specific vars).

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 when-to-use guidance: use when you need to search or list SimVars by query or category. It does not explicitly state when not to use it, but the sibling tools imply alternatives (e.g., get_simvar for a known SimVar value). No exclusions or prerequisites are mentioned.

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