wfs_add_layer

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

Despite no annotations, the description discloses important behaviors: filter is a QGIS expression (not OGC XML) and max_features caps server requests. It does not mention destructive actions or error handling, but the operation is non-destructive and straightforward.

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 brief and well-structured: a one-sentence purpose followed by bullet-like explanations of key parameters. Every sentence adds value without 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 tool's moderate complexity (7 params, simple operation) and presence of an output schema, the description covers the essential aspects. It could mention that the layer is added to the current project and is then manipulable by other tools, but this is implied.

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 carries the full burden. It explains url, typename, filter, and max_features clearly, but omits crs, version, and layer_name. This partial coverage leaves gaps, earning a middle score.

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 clearly states 'Add a WFS vector layer to the project', specifying both the action (add) and the resource type (WFS). The name and context differentiate it from sibling tools like wms_add_layer or wmts_add_layer.

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 explicit guidance on when to use this tool vs alternatives like wms_add_layer or other add-layer tools. It only mentions using ows_list_capabilities to list available typenames, but does not provide selection criteria or exclusions.

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