Set Layer CRS

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

With no annotations provided, the description carries full burden. It discloses the key behavioral trait that no reprojection occurs. This is essential for an agent to understand the tool's effect. However, it could further mention potential side effects like display issues if the original CRS was correct.

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?

Two sentences efficiently convey purpose and critical nuance. The description is front-loaded with the action and immediately follows with the important clarification. No extraneous words.

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 simple two-parameter input and no output schema, the description covers the core function and essential behavioral detail. It does not mention return values or error conditions, but for a straightforward setter with strong sibling differentiation, this is adequate.

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. It adds meaning to the 'crs' parameter via example 'EPSG:4326' but does not describe 'layer_id'. The example helps but does not fully cover both parameters, leaving some ambiguity.

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 verb 'Set' and resource 'CRS of a layer', includes an example format 'EPSG:4326', and explicitly distinguishes from reprojection operations. This differentiates it from sibling tools like 'get_layer_crs' and '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 a critical usage guideline: it clarifies that the tool does NOT reproject data, only changes interpretation. While it does not list alternative tools or explicitly state when not to use it, the clarification helps the agent avoid misuse.

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