windai-mcp

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

No annotations provided, so description carries full burden. Effectively discloses data source (3 years 2021-2023 reanalysis), authentication model (free, no API key), and return payload structure (mean speed, IEC class, etc.). Lacks rate limits, error behavior, or latency expectations.

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?

Four sentences with zero waste: purpose, return values, data provenance, and authentication. Front-loaded with core verb and scope. Every sentence adds distinct value not present in structured fields.

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?

Compensates well for missing output schema by enumerating return fields. Addresses auth/data source gaps left by missing annotations. Could improve with error handling or rate limit notes, but adequately complete for a free geospatial lookup tool.

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%, documenting ranges for latitude/longitude and defaults/typical ranges for hub_height. Description adds no parameter-specific guidance beyond implying global coverage, so baseline 3 is appropriate.

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?

Description opens with specific verb 'Get' + resource 'approximate wind resource estimate' + scope 'any location on Earth'. Clearly distinguishes from siblings: contrasted with compare_wind_sites (comparison), get_wind_farm_assessment (detailed project assessment), and pricing/model_info utilities.

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?

Provides implicit differentiation through specificity ('approximate', 'any location', 'historical reanalysis data'), but lacks explicit when-to-use guidance versus get_wind_farm_assessment or compare_wind_sites. No mention of prerequisites or exclusion criteria.

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