Set Project CRS

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

No annotations provided. The description mentions that changing the CRS affects how layers are projected, but does not detail any side effects, performance impact, or whether existing layers are reprojected.

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 concise sentences efficiently convey the core action and effect, with no unnecessary 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?

Covers the basic functionality and effect, but lacks details such as input validation, error handling, or whether changes are immediately visible. Given only one parameter and no output schema, it is somewhat adequate but not fully comprehensive.

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 parameter 'crs' has no description in the schema (0% coverage). The description adds value by clarifying it is a coordinate reference system and giving examples of valid values.

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 the tool sets the project CRS with examples like 'EPSG:4326' and explains the effect on layer projection. However, it does not explicitly distinguish from sibling tool 'set_layer_crs' which operates on individual layers.

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 versus alternatives (e.g., set_layer_crs) or when not to use it. The description only explains what it does.

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