Set Canvas Scale

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

The idempotentHint annotation already indicates safe repeated calling. The description adds that the tool modifies scale and rotation, but does not disclose any other behavioral traits. With annotations covering safety, this is adequate.

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 with no wasted words. The purpose and parameter details are front-loaded, making it easy for an agent to quickly understand and use the tool.

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 with no output schema and idempotentHint, the description covers input parameters adequately. It does not mention return value or side effects, but those are not critical for a straightforward tool.

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 description coverage is 0%, but the description adds valuable semantics: scale as denominator (e.g., 50000 for 1:50000) and rotation in degrees (0-360). This compensates for the schema gap, though minor details like expected value ranges are implicit.

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 sets the map canvas scale and/or rotation. The verb 'set' and resource 'map canvas scale and/or rotation' are specific, and the tool is well-distinguished from siblings like get_canvas_scale.

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 guidance on how to provide scale and rotation values, but does not offer explicit when-to-use or when-not-to-use guidance relative to alternatives like set_canvas_extent.

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