Get Canvas Extent

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

Annotations already declare readOnlyHint=true, so no destructive behavior. The description adds that the tool returns 'current map canvas extent and CRS', but this is minimal additional context. No contradictions with annotations, but the description does not elaborate on behavioral traits beyond what annotations provide.

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 a single, front-loaded sentence with no unnecessary words. Every part of the sentence contributes to understanding the tool's purpose. No repetition or fluff.

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 tool has an output schema, full explanation of return values is not required. However, with many sibling tools, a bit more context (e.g., use case for getting current view) would improve completeness. The description is minimally sufficient but could be more informative.

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?

There are no parameters, and schema coverage is 100% (empty object). The description adds meaning by specifying what the tool returns (extent and CRS), which is helpful given the lack of input parameters. Baseline for 0 parameters is 4, and this is appropriate.

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 tool retrieves the current map canvas extent and CRS, using a specific verb ('Get') and identifying the resource ('current map canvas extent and CRS'). It effectively distinguishes from sibling tools like 'get_canvas_scale' and 'set_canvas_extent', which are different operations.

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 implies usage (e.g., to get current view extent) but provides no explicit guidance on when to use this tool versus alternatives like 'get_layer_extent' or 'get_canvas_scale'. No exclusions or when-not-to-use information is given.

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