agriculture-mcp-server

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

Provides concrete behavioral details absent from annotations: soil depth range (0-54cm) and forecast horizon (1-16 days), though omits rate limiting or error 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?

Well-structured with purpose front-loaded, followed by specific metrics, use cases, and Args section; no redundant or filler content.

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 no output schema exists, description adequately specifies return values (soil temp, moisture, FAO evapotranspiration) for the tool's moderate complexity.

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?

Effectively compensates for 0% schema description coverage by providing concrete examples (Berlin coordinates) and constraint documentation (1-16 range, default 7) for all parameters.

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?

Clearly states it retrieves current and forecasted soil conditions (temperature at 0-54cm depth, moisture, evapotranspiration), specifically distinguishing it from climate and crop weather siblings.

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?

Explicitly identifies ideal use cases (sowing decisions, irrigation planning) but lacks explicit guidance on when to prefer crop_weather_forecast or climate tools instead.

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