set_scale

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

With no annotations, the description fully discloses behavior: the exclusive choices, coordinate system (image px at render scale 2.0, origin top-left, y down), and that sheet payloads have both px and pt dimensions.

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?

Every sentence serves a purpose, front-loaded with the key 'exactly ONE of' constraint, followed by necessary context. No wasted 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?

Tool is well-defined for selection and invocation without output schema; covers all four modes, coordinate system, and behavioral rules.

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 coverage is high (80%), and description adds value by explaining the exclusive nature of parameters, the meaning of 'use_detected', and example format for 'label'. Minor gap: no detailed explanation of calibrate object beyond what schema has.

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?

Description clearly states the tool sets a sheet's scale, lists four exclusive methods (label, upp, calibrate, use_detected), and differentiates from siblings like delete_shape or export_takeoff.

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?

Explicitly tells to use exactly one of the four methods, notes that detected scale is never automatic, and explains coordinate system context for proper invocation.

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