Linear Dimension

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

Annotations indicate readOnlyHint=false (mutation), which the description supports with 'Create'. It adds tolerance context (ISO 129 and ISO 286 fit) but fails to disclose other behavioral traits like prerequisites (open drawing) or that the dimension is an entity added to the drawing.

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 a single, front-loaded sentence that efficiently conveys the core action and optional feature. Every word is meaningful, with no redundancy or filler.

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 complexity (13 parameters, 6 required) and the presence of an output schema, the description is minimal. It omits spatial context (e.g., points define extension lines, dim_x/dim_y position the dimension line) that would help an agent fully understand the geometry.

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 100% with detailed parameter descriptions (e.g., fit, tol_mode). The description adds no new parameter information beyond mentioning tolerance standards, so it does not compensate beyond the baseline for schema-rich tools.

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 states 'Create a linear dimension, optionally toleranced', which is a specific verb ('Create'), a distinct resource ('linear dimension'), and a key distinguishing feature ('optionally toleranced'). This differentiates it from sibling tools like 'dimension_aligned' and 'dimension_angular'.

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 no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or suggest alternative tools for different scenarios, such as 'dimension_aligned' for rotated measurements.

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