generate_map_series

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

With no annotations and no output schema, the description carries full burden. It does disclose useful behavior: output files are numbered by drawing order, each sheet is registered in the QGIS Layout Manager, and basemap tiles require internet. It omits overwrite behavior, file naming, runtime cost, and what is returned on success.

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 lead sentence is front-loaded with the core behavior, followed by a tight, example-driven Args list with no filler. The QGIS Layout Manager sentence is arguably secondary but still earns its place by explaining a side effect.

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?

For a 9-parameter generation tool with no annotations and no output schema, the description covers purpose and roughly half the parameters. Missing are defaults for output formatting (dpi, format, page_size, orientation) and the meaning of 'sources', leaving real gaps an agent must guess at.

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 the description must compensate and it only partially does: it explains output_dir (numbered by drawing order), layers (defaults to all added layers), context_layers (with a concrete example) and basemap (the three allowed values plus an internet caveat). Five of nine parameters — dpi, format, sources, page_size, orientation — get no semantic explanation anywhere.

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?

States a specific verb and resource ('Render one map per thematic layer') and clarifies the unit of output (a series, one sheet per layer), which implicitly distinguishes it from the single-map sibling generate_map. It does not explicitly name that sibling or state the boundary, so it falls short of a 5.

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 'one map per thematic layer' phrasing implies this is the batch/multi-layer variant versus generate_map, and the context_layers/basemap args hint at cartographic reuse, but the description never states when to pick this tool over generate_map, nor any prerequisites other than internet for basemaps.

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