Get Raster Info

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

Annotations indicate readOnlyHint=true, consistent with description. Description adds value beyond annotations by detailing exact information returned (band count, dimensions, CRS, extent, per-band statistics, nodata values). No contradictions.

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?

Description is a single sentence listing key attributes without any extraneous words. Every part earns its place.

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 an output schema exists, return value explanation is not needed. Description covers major categories of raster info. However, could mention that this only works for raster layers and that the layer must be loaded, but current detail is sufficient.

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?

Single parameter layer_id is self-explanatory, but schema description coverage is 0% and description does not elaborate on what layer_id represents. Baseline score applies as parameter meaning is implied but not explicitly clarified.

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?

Clearly states 'Get raster layer info' and enumerates specific attributes: band count, dimensions, CRS, extent, per-band statistics, nodata values. Distinguishes from sibling tools like get_layer_crs or get_layer_extent which return only one attribute.

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 explicit guidance on when to use this tool vs alternatives. Sibling tools like get_layer_crs or get_layer_extent exist, but description does not advise when to prefer this comprehensive tool over those specific ones.

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