raster_band_statistics

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

No annotations exist, so description carries full burden. It mentions source can be local or URL, but fails to disclose behavior regarding nodata values, file format restrictions, performance implications, or error handling. Minimal behavioral context beyond the basic calculation.

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?

Two clear sentences with a structured parameter list. Every sentence earns its place; no fluff. Front-loaded with the core function.

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 simple statistics tool with one parameter and an output schema (not shown but present), the description covers the essential operation. However, it omits details like band interpretation, nodata handling, and coordinate reference system implications, leaving some ambiguity.

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 0%; description only adds that source is a path (local or URL). This is marginal value over the raw schema, which already shows a string parameter. No details on accepted formats, patterns, or constraints.

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 verb (calculate) and the resource (raster) and specifies the outputs (min, max, mean, std for each band). It effectively distinguishes from sibling tools like 'raster_histogram' and 'zonal_statistics'.

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?

No guidance on when to use this tool versus alternatives (e.g., focal_statistics for local windows, raster_histogram for distribution, zonal_statistics for zones). No when-not-to-use or prerequisites mentioned.

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