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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so safety is covered. The description adds valuable return information (filename, size, timestamps, page token) and default ordering, which matters because there is no output schema. It does not mention auth or rate limits.

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, front-loaded with purpose and default ordering. Return details, use case, and prerequisite source follow. The example values are somewhat redundant with the schema examples but not wasteful overall.

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 list tool with no output schema, the description explains return values and pagination, states the default sort, and names the prerequisite source for dataset and version. Annotations cover safety. An agent has enough to invoke it correctly.

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 all seven parameters are documented in the schema. The description repeats example dataset/version values and default sorting but adds little parameter-specific syntax beyond what the schema already provides. 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?

States a specific verb ('List the files') and resource ('one KNMI Data Platform dataset'), with scope ('newest first by default'). It distinguishes itself from sibling knmi_datasets by directing users there for dataset and version, and frames its use before downloading. An agent can tell what this tool does without opening the schema.

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 says to get dataset and version from knmi_datasets and gives a clear use case: finding the most recent radar composite, observation file, or model run before downloading. No explicit when-not guidance or named download alternative (knmi_file_url), but the context is clear enough.

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