set_map_scale

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

No annotations provided, so description must disclose behaviors. It mentions that it updates the .aprx project when save=true and uses arcpy.mp. However, it lacks details on failure modes, permissions, or effect on temporary changes beyond the save flag.

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, concise and front-loaded: first sentence states the action and method, second gives usage and side effect. 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?

Given the tool's simplicity and the presence of an output schema, the description adequately covers the purpose, usage context, and save behavior. It omits details on error handling or what happens if the map frame is not found, but overall is sufficient for the task.

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 input schema has detailed descriptions for each parameter, so baseline is 3. The tool description repeats the scale denominator concept but adds little new beyond the schema. The usage context ('before export') is helpful but not directly about parameter meaning.

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 verb and resource: 'Set the camera scale denominator for a selected layout map frame'. It also distinguishes its purpose from sibling tools like set_layout_size or export_layout_pdf by specifying it's about fixing a known scale for exporting.

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?

Provides explicit context for when to use: 'before exporting a layout when the map must be fixed to a known scale'. It does not mention when not to use or alternatives, but the guidance is clear for the primary use case.

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