dissolve_layer

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

The description goes well beyond the annotations by disclosing that the aggfunc choice is recorded in the manifest, that features with a null by key are dropped and counted, and that the output feature count is verified against distinct keys so a wrong grouping fails loudly. These failure-mode details are not available elsewhere and do not contradict the 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 front-loaded with the core operation and every subsequent sentence adds a concrete behavioral caveat: manifest recording, null dropping, and fail-loud verification. There is no filler, redundancy, or wasted wording.

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?

Together with the provided annotations and output schema, the description covers parameter semantics, null behavior, aggregation defaults, and failure mode, which is enough for an agent to select and invoke the tool correctly. Missing details are either schema-present or non-essential for correct invocation.

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 carry the burden. It does this well by explaining the two non-obvious parameters: `by` as the grouping value with null meaning one feature in all, and `aggfunc` as an enumerated aggregation with 'first' as the default. `input_path` and `output_path` are left to their self-explanatory names, which is acceptable but not fully elaborated.

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 opens with a specific verb and resource: 'Merge features into one geometry per value of `by`' and also specifies the all-features fallback. This clearly distinguishes dissolve_layer from sibling tools like explode_layer and merge_layers even without naming them.

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 communicates that this is the dissolve-by-attribute operation and clarifies when a null grouping key dissolves all features into one. However, it does not explicitly name alternatives or state when not to use this tool, so usage guidance is implied rather than direct.

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