Set Layer CRS

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

Without annotations, description discloses key behavioral trait: does not reproject data, only reinterprets coordinates. Informative but could mention potential risks of incorrect CRS assignment.

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, front-loaded with critical caveat. No wasted 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?

Adequate for a simple tool with no output schema. Covers the essential behavioral nuance. Might assume existence of layer but that is implicit.

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% but description provides example for 'crs' parameter. Does not clarify 'layer_id' beyond its type. Partial value added.

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?

Clearly states verb 'Set', resource 'CRS of a layer', provides example 'EPSG:4326', and crucially distinguishes from reprojection. Differentiates from sibling tools like set_layer_property and transform_coordinates.

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?

Explicitly states when to use (to change CRS interpretation) and when not to use (if reprojection needed). However, does not name specific alternative tools for reprojection, leaving slight ambiguity.

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