rhino_dimension_style

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

The description states the core behavior: it opens the annotation styles manager, which implies a UI action rather than a geometric mutation. However, with no annotations, it does not disclose whether the manager is modal, whether it modifies document state, or whether an open document is required.

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 with no filler or repetition. It efficiently communicates the action and target.

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-parameter tool with an output schema, the description does not need to explain arguments or return values. It is still only minimally complete because it offers no behavioral context and does not disambiguate from the near-identical sibling rhino_annotation_dimension_style.

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 takes zero parameters and the schema is empty, so there are no parameter semantics for the description to add. This is the appropriate baseline for a no-argument tool.

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 uses a specific verb ('Open') and a named resource ('Annotation Styles (dimension style) manager'), so an agent can tell this invokes a UI panel. It does not explicitly contrast with the similarly named sibling rhino_annotation_dimension_style, so it stops short of full differentiation.

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 guidance is given about when to use this tool versus alternatives such as rhino_annotation_dimension_style or other annotation-related commands. The intended usage is only implied by the generic verb 'Open'.

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