Aligned Dimension

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

The description clearly discloses that the operation creates a dimension entity, which is consistent with readOnlyHint=false. It adds the behavioral nuance that the dimension reflects true distance rather than a projected distance, though it does not mention side effects like placement on the current layer or associativity.

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; every phrase ('aligned dimension', 'true distance', 'between two points') carries meaning. It is appropriately sized for the tool's complexity.

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?

For a low-complexity creation tool, the description plus fully documented parameters and output schema cover the necessary calling context. The main omission is an explicit note that the dimension is created in the current drawing and uses current dimension settings, but these are reasonable defaults for a CAD tool.

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% and the schema descriptions already explain the point coordinates and dimension-line position. The description adds only the conceptual 'two points' context, so the baseline 3 is appropriate.

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 opens with a specific verb and resource ('Create an aligned dimension') and clarifies the exact geometric behavior: it measures the true distance between two points. This distinguishes it from horizontal/vertical linear dimensions and other dimension siblings, even without naming them.

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 phrase 'true distance' implies it is intended for measuring points that are not orthogonally aligned, but it never states when to choose this over dimension_linear or dimension_auto, nor does it mention exclusions. Usage is implied rather than explicit.

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