Set Layer CRS

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

No annotations are provided, so the description carries the full burden. It explicitly states that the tool does not reproject data, a key behavioral trait. It also provides an example CRS value ('EPSG:4326') for clarity. However, it does not mention whether the operation is reversible or if any permissions are needed, but for a simple CRS assignment, this level of transparency is adequate.

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 extremely concise: two short sentences. The first sentence states the action, the second clarifies what it does NOT do. No unnecessary words. Front-loaded with the core verb and resource.

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 simple tool with 2 parameters and no output schema, the description covers the essential behavior (what it does, what it doesn't do). It gives a practical example for the CRS parameter. It could be more complete by clarifying that layer_id must refer to an existing layer, but that is reasonable to assume. The description is largely sufficient for the tool's simplicity.

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%, meaning no parameter descriptions in the schema. The tool description only mentions 'crs' with an example ('EPSG:4326') but does not describe 'layer_id' or provide any format or constraints. With only 2 parameters, the description should compensate fully, but it partially fails for 'layer_id'.

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?

Description clearly states the tool's action: 'Set the CRS of a layer (e.g. 'EPSG:4326').' It also explicitly distinguishes from reprojection: 'This does NOT reproject data — it only changes how the layer's coordinates are interpreted.' This differentiates it from siblings like transform_coordinates or set_project_crs.

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 provides context for when to use the tool (changing CRS interpretation without reprojection) but does not explicitly mention when not to use it or name alternative tools. The 'does NOT reproject' note implicitly guides usage, but direct comparison with siblings like set_project_crs or transform_coordinates is absent.

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