Set Project CRS

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

No annotations provided. Description states it changes how layers are projected on the map canvas, but does not disclose if it reprojects only visually or modifies underlying data, nor any side effects like performance impact or irreversible changes.

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 action, no filler. Every word contributes to clarity.

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 setter tool with one parameter and no output schema, the description adequately explains what it does and gives examples. Could mention effect on existing layers or canvas refresh, but overall sufficient.

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% for parameter description, but the description adds meaning beyond type: 'e.g. 'EPSG:4326', 'EPSG:3857'' clarifies the format of the string 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 uses specific verb 'Set' and resource 'project coordinate reference system' with examples ('EPSG:4326', 'EPSG:3857'), clearly distinguishing from sibling tool set_layer_crs which sets a layer's 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?

No guidance on when to use this tool vs alternatives (e.g., set_layer_crs). No description of prerequisites, effects on project layers, or when not to use.

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