set_drawing_scale

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

No annotations are provided, so the description carries the full burden. It says 'set' (a mutation) but does not disclose whether the change is persisted, whether it affects existing entities, whether it requires an open drawing, or whether it is reversible.

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?

A single, front-loaded sentence with no filler. Efficient, though it is arguably too terse given the missing usage and behavioral detail.

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 tool is simple (one required numeric param), so the description is minimally viable, but with no annotations and no output schema, it should say more about the effect and persistence of the change and the state required to call it.

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% for the single 'scale' parameter, so the description must compensate. It does clarify the semantic meaning of the value (a ratio between local drawing units and world coordinates), which is genuinely useful, but gives no units convention, expected value range, or example.

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?

States a specific verb+resource ('Set a drawing scale factor') with a clear scope qualifier ('between local drawing units and world coordinates'). An agent can identify the operation, though there is no explicit differentiation from related siblings like add_scale_bar or create_viewport.

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?

No when-to-use guidance, no prerequisites (e.g. must a drawing/document be active), and no alternatives named. The agent has to infer context of use entirely on its own.

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