Set Canvas Scale

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

Annotations already indicate idempotency (idempotentHint: true). The description adds parameter constraints (scale denominator format, rotation range) which go beyond annotations, but does not contradict them. It is transparent about input expectations.

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 only two sentences, front-loaded with the action and followed by parameter details. Every sentence adds value without redundancy or unnecessary information.

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?

The description covers the core functionality and parameter constraints. For a simple setter with no output schema, it is nearly complete. Minor omission: it does not clarify behavior when both parameters are null (likely no change), but this is acceptable given the schema defaults.

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 schema describes parameters with no descriptions (0% coverage). The description compensates by explaining that scale is a denominator (e.g., 50000 for 1:50000) and rotation is in degrees 0-360, adding essential semantic meaning for correct usage.

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 map canvas scale and/or rotation, using a specific verb and resource. It distinguishes from sibling tools like set_canvas_extent or zoom_to_layer by focusing solely on scale and rotation.

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 format details for parameters (scale denominator, rotation range), indicating when to use the tool. However, it lacks explicit guidance on when not to use it or alternatives, such as set_canvas_extent for extent changes.

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