add_vector_layer

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

With no annotations, the description carries the full behavioral burden. It does disclose the primary side effect: adding a layer to the active map. But it does not mention prerequisites like requiring an existing active map, error behavior for invalid paths, or whether the operation is destructive to existing layers. This is adequate but has clear gaps.

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 short, front-loaded with the main purpose, and includes a clearly formatted Args section. Every sentence adds useful information without redundancy or filler.

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?

The tool has a single well-documented parameter, an output schema exists, and the operation is simple. The description covers the essential purpose and path semantics. It only lightly assumes the agent understands 'active map' semantics, but this is not a serious gap for this low-complexity tool.

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?

The input schema only provides a 'Path' string with no description, while the tool description meaningfully explains that path is a full path to the data source and gives concrete examples. This adds real value beyond the schema for the only parameter.

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 the action ('Add'), the resource ('vector layer'), and the destination ('active map'), and lists concrete formats (shapefile, feature class, GeoJSON). This distinguishes it from siblings like add_raster_layer without needing to inspect either tool's schema.

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 vector-specific formats imply when this should be used, and the sibling list includes add_raster_layer, so an agent can infer the raster/vector distinction. However, the description does not explicitly state when to use this tool over alternatives or mention any exclusions, so usage guidance is only implicit.

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