hillshade

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

With no annotations provided, the description must fully disclose behavior. It only states the basic operation and return value, but does not disclose performance implications, side effects (e.g., file writing), or error conditions. For a raster processing tool, this is insufficient transparency.

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 follows a clean docstring format with Args and Returns sections. It is concise yet covers the key parameters and output. A minor improvement would be removing redundancy, but overall it is well-structured and information-dense.

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 the existence of an output schema, the description adequately explains the return value. It covers inputs, outputs, and the optional save behavior. For a tool of moderate complexity, it is mostly complete, though it could mention supported raster formats or CRS handling.

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 schema has 0% description coverage, so the description adds essential meaning. It explains raster_path, azimuth (in degrees), angle_altitude (in degrees), and output_path (optional). However, it omits value ranges (e.g., azimuth 0-360, altitude 0-90) and defaults, which could help the agent use the tool correctly.

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 ('Generate hillshade') and the input resource ('from a DEM raster'). Among sibling tools like compute_ndvi or reclassify_raster, this tool has a distinct purpose, and the description effectively communicates its specificity.

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 lacks any guidance on when to use this tool versus alternatives (e.g., slope or aspect). It does not mention prerequisites like CRS requirements or coordinate system, nor does it address limitations such as memory constraints for large rasters.

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