stac_download_composite

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

No annotations exist, so description carries full burden. Discloses band order mapping, cloud_mask limitation (Sentinel-2 only), output formats, and return format. Lacks explicit statements on side effects or auth needs, but overall 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?

Well-structured with sections (Description, Args, Returns, Tips, Example). Slightly long but every sentence adds value. Could be slightly more concise, but appropriate for complexity.

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 no output schema and no annotations, description covers parameters, usage, return format, and alternatives. Lacks error handling or invalid input behavior, but sufficient for agent invocation.

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 has 0% description coverage, so description must compensate. It explains all parameters: scene_id from search, bands with examples, composite_name, bbox, output_format, cloud_mask, output_mode. Adds recipes and tips beyond schema.

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 'Download a multi-band composite from a scene' and explicitly distinguishes from siblings like stac_download_rgb and stac_compute_index, making the purpose 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?

Provides explicit guidance: 'For true-colour RGB, use stac_download_rgb instead' and 'For single-value analysis, use stac_compute_index'. Also suggests using stac_describe_collection to see recipes, offering alternatives and context.

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