windai-mcp

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

No annotations provided, so description carries full burden. It discloses the ML model nature (deep learning, training data) and auth requirements (API key). However, it omits critical operational traits: read-only status, expected latency (likely slow for ML inference), cost/credits, rate limits, or whether results are cached/persisted.

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?

Three sentences with zero waste: sentence 1 defines the action and model context, sentence 2 details outputs (compensating for lack of output schema), sentence 3 states the auth requirement. Every clause 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?

For a complex 9-parameter tool with no output schema and no annotations, the description adequately compensates by listing specific return metrics (hourly CFs, AEP, P50/P90). However, it could improve by describing the response structure format or error conditions given the lack of output schema.

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%, establishing a baseline of 3. The description mentions the API key requirement (redundant with schema) but does not add semantic context for coordinate precision, turbine parameter relationships, or validation rules beyond what the schema already documents.

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?

Excellent specificity: 'Run a full WindAI AI-powered wind resource assessment' provides clear verb, resource, and scope. The detailed output list (AEP, P50/P90, diurnal profiles) distinguishes this from sibling 'get_wind_estimate' and implies this is the comprehensive option versus the quick estimate alternative.

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 term 'full' implies use for comprehensive analysis versus quick checks, and the API key requirement gates usage, but there is no explicit guidance on when to choose this over 'get_wind_estimate' or 'compare_wind_sites'. No prerequisites (e.g., valid coordinates) or exclusions are stated.

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