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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds genuine context: 'Keyless' (no credentials required) and the return payload shape (id, title, temporal/spatial extent). It does not discuss pagination behavior beyond what the schema says, which keeps it from a 5.

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?

Three front-loaded sentences that lead with the action and scope, then the return contract, then the authority claim. Efficient overall; the closing 'the catalogue itself, not a description of it' is slightly rhetorical but does reinforce trustworthiness.

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?

No output schema exists, yet the description enumerates the returned fields (collection id, title, temporal/spatial extent), and annotations cover safety while the schema covers all three params. An agent has everything needed to call and consume this tool 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 limit, query and offset are already fully documented with ranges, defaults and semantics. The description adds no parameter-level detail beyond echoing that search is keyword-based, so the baseline 3 applies.

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 pair (list / keyword-search) and resource (Copernicus Climate Data Store catalogue), quantifies scope (~140 published climate datasets) and even names example dataset families. An agent can distinguish it from cds_collection and cds_submit_request immediately, since the description says the id it returns is what those tools consume.

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 declares itself AUTHORITATIVE for the question 'which Copernicus/C3S dataset covers X' and routes downstream: 'pass it to cds_collection or cds_submit_request'. That is a clear when-to-use plus named alternatives, leaving little to inference.

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