Katzilla MCP

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds valuable context beyond annotations: it specifies the return format ('Katzilla envelope { data, quality, citation }'), explains quality metrics ('freshness/uptime/confidence'), and details citation components ('source URL, license, SHA-256 data hash'), which aids in understanding output behavior and auditability.

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 efficiently structured into two sentences: one stating the purpose and return metadata, and another detailing the source, update frequency, and output format. It is front-loaded with the core functionality and avoids unnecessary repetition, though the second sentence is slightly dense with multiple details packed together.

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 (read-only list operation with two parameters), rich annotations (covering safety and idempotency), and the presence of an output schema (implied by 'Has output schema: true'), the description is complete. It explains the purpose, data source, update frequency, and detailed return structure, compensating for any gaps without needing to reiterate schema or annotation information.

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%, with clear descriptions for both parameters ('limit' and 'query'). The description does not add any parameter-specific semantics beyond what the schema provides (e.g., no examples or formatting details for the query). With high schema coverage, the baseline score of 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 specific action ('List available dataset collections'), resource ('from the Copernicus Climate Data Store (CDS)'), and scope ('Returns collection metadata including temporal and spatial extent'). It distinguishes itself from sibling tools by focusing on Copernicus datasets, unlike other environment tools (e.g., weather, air quality).

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 implies usage context through the agent label '[Environment & Air Quality Agent]' and mentions the data source and update frequency ('updates daily'), but does not explicitly state when to use this tool versus alternatives (e.g., other Copernicus tools or environmental data sources). No exclusions or prerequisites are provided.

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