gugik_download_lidar

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

No annotations provided, so description carries full burden. Discloses return behavior (links vs local files), coordinate system, variants, and that tool doesn't add layers to QGIS. Missing details on max_samples effect and error conditions.

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?

Single paragraph with efficient wording, front-loaded purpose. Could benefit from structure (e.g., bullet points) but no wasted sentences.

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?

Output schema exists but not described. Description covers main behaviors and references sibling tool for mechanism, but leaves max_samples unexplained and lacks details on output format. Adequate but with gaps.

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 coverage is 0%, so description must compensate. Explains bbox format, variant options, output_dir behavior, but does not explain max_samples. Three of four parameters benefit from description.

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 it finds and optionally downloads LIDAR point-cloud (LAZ) packages covering a bounding box. References sibling tool for mechanism differentiation. Specifies variants and coordinate system.

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?

Implies similarity to 'gugik_download_nmt_tiles' and describes when to use output_dir vs not, but lacks explicit when-to-use or alternatives among many siblings.

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