rhino_add_dimension_linear

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

With no annotations, the description must disclose behavior itself, but it only states that a placement mode is entered. It does not say what happens next, whether a dimension is immediately created, whether the command blocks awaiting user clicks, or what state changes occur.

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 entire description is one short sentence and is front-loaded with the essential action and resource. There is no redundant wording or structured 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?

For a zero-argument mode-entry tool, the description gives the bare minimum needed to know what command to invoke. However, it lacks context about the interactive nature of placement mode and does not mention how this relates to other dimension tools, leaving the agent to guess about the resulting behavior.

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 tool has zero parameters and the schema covers them completely, so the description does not need to add parameter documentation. The baseline for a no-parameter tool is therefore 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 identifies a specific action ('enter placement mode') and resource ('linear dimension'), so an agent can tell it is not adding an angular, aligned, or radial dimension. It remains slightly ambiguous whether this creates a dimension or starts an interactive mode, and it does not distinguish itself from the similarly named rhino_dimension_linear.

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 gives no explicit guidance about when to choose this tool over alternatives such as rhino_dimension_aligned or rhino_dimension_linear. There is no mention of prerequisites, workflow context, or whether the user must interact with the Rhino viewport after the mode starts.

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