list_modelsList the weather models windext reads by default at a location, including their resolution and coverage notes.
Which weather models windext reads by default at a location, and their resolution/coverage notes.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | ||
| lon | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the agent knows this is a safe, deterministic read operation. The description adds that models are read 'by default' and mentions resolution/coverage notes, which is useful context beyond the annotations, but doesn't disclose any constraints on the location input or caching behavior.
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?
A single efficient sentence with the core purpose front-loaded. No wasted words, though it could be slightly clearer on the action verb.
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 read-only, 2-param tool with no output schema, the description covers the core purpose and the locational dependency. However, with 0% schema coverage and no output schema, the agent has little detail on the exact return structure (model names, resolution format, coverage area units) or the expected lat/lon convention, leaving gaps for correct 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 description coverage is 0% and the schema provides only type and range constraints for lat/lon with no semantic descriptions. The description says models are read 'at a location' but doesn't explain that lat/lon are coordinates, their format, or coordinate system. It adds minimal meaning beyond the schema's constraints.
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 resource ('weather models windext reads by default') and what it returns ('resolution/coverage notes'). It's clear and distinguishable from siblings like find_spot or spot_forecast, though 'list_models' as a verb is somewhat passive.
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 phrase 'by default at a location' implies usage context tied to a lat/lon, but there is no explicit guidance on when to call this versus alternatives like spot_forecast. The agent must infer that this is for discovering default model configuration.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.