build_qgis_review

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

No annotations exist, so the description carries the full burden, and it does disclose non-obvious behavior: it uses the canonical QGIS subprocess, treats absent registrations as explicit non-matches rather than successes, preserves existing SVG bindings, and refuses to invent new semantic symbol assignments. It still omits overwrite/destructive behavior on output_path and any permission or failure-mode details.

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?

Three sentences, front-loaded with the action, with no filler. The phrasing is terse and somewhat gnomic ("An absent registration stays explicit"), but each sentence carries a distinct behavioral point.

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, so return values need no explanation, and the preservation semantics are covered. But for a five-parameter build/conversion tool with no annotations, the description leaves input roles (project vs. OSM data vs. output path) and workspace preconditions unstated, which an agent needs to call it 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 for five undocumented parameters, and it does not. It never mentions project_path, osm_data, output_path, standalone, or matching_context_path, leaving their meaning and required-ness entirely to the bare titles.

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+resource ("Build a new offline QGIS review") and adds scope ("preserve matched or uncorrected identity"). The "build/create" framing implicitly distinguishes it from verify_qgis_review and start_review_server, though it stops short of naming those siblings explicitly.

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?

No when-to-use guidance, no prerequisites, and no alternatives named. The agent can infer this is the creation step preceding verify_qgis_review, but nothing in the text states the ordering or selection conditions.

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