Katzilla MCP

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds valuable behavioral context beyond this: it specifies the data source (NOAA National Centers for Environmental Information), update frequency ('updates daily'), and details about the return format ('Katzilla envelope { data, quality, citation }') including quality scores and citation components. This enhances transparency without contradicting annotations.

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 front-loaded with core purpose, efficiently covers key details (scope, source, updates, return format), and uses every sentence purposefully without waste. It balances completeness with brevity, making it easy for an agent to parse.

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 complexity (6 parameters, annotations, and an output schema), the description is complete. It covers purpose, scope, source, update frequency, and return structure. With annotations providing safety hints and an output schema presumably detailing the 'Katzilla envelope,' no critical gaps remain for agent understanding.

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%, so the schema fully documents all parameters. The description does not add any parameter-specific semantics beyond what the schema provides (e.g., it doesn't explain dataType codes like 'TMAX' or locationId formats). Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 the tool's purpose: retrieving historical weather and climate observations (specific verb) from NOAA CDO (resource) for US locations. It distinguishes from siblings by specifying 'daily temperature, precipitation, snowfall, and wind' and being the 'largest archive of US weather data,' setting it apart from other environment tools like environment__canada-weather or environment__openaq.

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 context for usage: 'Historical weather and climate observations... for any US location' and 'updates daily.' It implies when to use (for US historical weather data) but does not explicitly state when not to use or name specific alternatives among siblings, such as environment__canada-weather for non-US data or environment__openmeteo-aq for air quality.

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