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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context: the filtering logic (case-insensitive substring), the default behavior when keyword is omitted (returns only Sentinel mission collections), and the auth requirement ('no auth required'). These details are not in the annotations, enhancing transparency about how the tool behaves.

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 composed of three sentences that are direct and purposeful. The first sentence establishes the tool's purpose and scope, the second explains how to use the results, and the third provides data provenance and auth info. There is no fluff or redundancy, and it is appropriately compact for the information conveyed.

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 browse/list operation with two optional parameters and an output schema, the description is sufficiently complete. It covers the data source, auth, filtering behavior, and the connection to downstream tools. It doesn't mention pagination or result ordering, but these are likely conveyed by the output schema, and the complexity is low. A minor gap is the lack of explicit guidance on when to use this tool versus searching directly, but overall it provides enough context for correct usage.

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%, and the schema already provides detailed descriptions for both 'limit' and 'keyword', including examples and default behavior for keyword omission. The tool description does not add new information about parameters beyond what the schema provides; it simply re-states the filtering capability. Since the schema carries the load, the 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?

The description clearly states the action ('Browse...catalog of satellite/product collections') and the resource (Copernicus Data Space Ecosystem STAC catalog). It lists specific mission types (Sentinel-1, Sentinel-2, etc.) and mentions the tool is filterable by keyword. This distinguishes it from sibling tools like search_scenes and scene_detail by explicitly saying the returned IDs are used with those tools, making its role as a collection-listing precursor unambiguous.

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 implicitly indicates when to use this tool: to discover collections and obtain IDs for subsequent calls to search_scenes and scene_detail. It doesn't explicitly state when not to use it or compare it to alternatives, but the relationship to those siblings is clear. This provides enough guidance for an agent to select it when a user wants to browse available imagery collections, though a more explicit 'use this when you need...' would be ideal.

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