clip_layer

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

Beyond the annotations (idempotentHint=true, destructiveHint=false, readOnlyHint=false), the description discloses meaningful behavior: automatic CRS alignment, refusal of inputs without a CRS, and the warnings key with hints about empty results or non-overlapping extents. This gives the agent important runtime expectations. No contradiction with annotations.

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 is compact and front-loaded: the core operation is stated in the first sentence, and the second paragraph efficiently covers warnings and CRS restrictions. Every sentence adds useful information; there is no fluff or redundancy.

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 simple three-parameter input, the presence of an output schema, and annotations covering idempotency and destructiveness, the description covers the essential caveats: CRS handling, refusal behavior, and warning semantics. Nothing critical appears missing for an agent to invoke and interpret the tool correctly.

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%, so the description must compensate. It clarifies roles by naming 'a layer' and 'a mask layer', and adds the CRS requirement for inputs. However, it does not directly explain each path parameter or the meaning of output_path, relying on self-explanatory parameter names. Partial compensation only.

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 uses a specific verb ('Clip') and resource ('a layer' clipped to 'a mask layer'), making the core action clear. It also adds relevant CRS alignment context. However, it does not explicitly distinguish this tool from sibling spatial operations like overlay_layers or spatial_join, so it stops short of full differentiation.

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 use case is implied by the name and first sentence: clip when you need to cut a layer to a mask extent. It also states prerequisites (inputs must have a CRS) and warning behavior. But it never explicitly says when to use this tool versus alternatives, nor lists exclusions or alternatives.

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