cad_sketch_dimension

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

No annotations are provided, and the description lacks disclosure of behavioral traits such as whether the tool mutates the sketch, what prerequisites are needed (e.g., an active sketch), error scenarios, or if it is idempotent. The phrase 'driving dimension' implies constraint, but more context is needed.

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, well-structured sentence that front-loads the key purpose and immediately provides usage details in parentheses. Every word adds value, with no repetition or fluff.

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 no output schema, the description covers most parameters and core behavior. It lacks explanation of the return value (e.g., what the tool returns after adding a dimension) and does not describe 'sessionId'. Overall, it is fairly complete for a dimension-adding 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?

The description adds significant meaning beyond the schema by explaining the 'kind' enum options, how 'entity' and 'entity2' are used (e.g., distance requires two entities), and the format of 'value' (inches or expression). However, 'sessionId' is not mentioned, and 'entity' IDs are not explained.

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 'Add a driving dimension' and explains the different kinds (length, radius, etc.). It distinguishes the tool from siblings like cad_sketch_line or cad_sketch_circle by focusing specifically on dimensions.

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 explicit guidance on which kind to use for different geometry types (line, circle, etc.) and explains value formats. However, it does not mention when not to use this tool or offer alternatives, such as using a reference dimension or constraints.

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