download_copernicus_granule

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

With no annotations, the description carries the behavioral disclosure burden and does a good job: it reveals credential requirements, that the tool generates a URL and curl command rather than necessarily downloading directly, and that the return is a JSON string with a verified endpoint, authorization header, and execution instructions. It does not cover error cases or rate limits, but the core behavior is transparent.

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 compact and well-organized: an action-oriented opening sentence, a credential prerequisite, an Args section, and a Returns section. Every sentence contributes useful information without redundancy or filler.

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 single-parameter tool with an output schema, the description is largely complete: it explains the parameter format, credential prerequisite, and return contents. Missing details include what happens if credentials are absent or invalid and how the returned curl command should be executed, but these are reasonable gaps given the tool's simplicity.

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?

The input schema only provides a string property with no description, so the description adds crucial meaning: product_id is an official Copernicus UUID or product name, and it gives a concrete real-world example format. This fully compensates for the 0% schema description coverage.

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 a specific verb and resource: generate an authenticated download URL and curl command for a full Sentinel/Copernicus product package from CDSE. It distinguishes itself from siblings like stac_search or query_nasa_opera by focusing specifically on product-package download with credentials.

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 gives clear context: use this when you need to download an official Copernicus granule, and it explicitly notes the prerequisite of CDSE credentials configured via environment variables or configure_credentials(). It does not explicitly name alternatives or exclusions, but the purpose is specific enough for an agent to route correctly.

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