Styles: Set Current Dimension Style

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

With only readOnlyHint=false in annotations, the description carries the load and delivers: it mutates $DIMSTYLE, applies on both engines, per-dimension tolerances/fits/text overrides still override, refuses unknown styles, and reports previous and changed. None of this is derivable from structured fields.

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?

Three dense sentences, front-loaded with the primary effect before the caveats and refusal. Content earns its place, though the 'what a live seat's DIMSTYLE Restore does' analogy adds length without much distinct information.

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 one-parameter mutation tool with an output schema, the description covers what changes, what still overrides it, the failure condition, and the return fields. Nothing an agent needs to invoke it correctly is missing.

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 single 'name' parameter is already documented as case-insensitive in the schema. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource plus the precise effect: sets $DIMSTYLE and loads the style's variables as current DIM* settings. It also names the affected downstream tools (dimension_* and dimension_auto) and distinguishes itself from dimstyle_list/create/modify by describing the restore-style behavior.

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?

Makes the use case clear (make a style current so dimension_* draws with it) and states a prerequisite condition — it refuses a style the drawing does not hold. It does not explicitly route to siblings like dimstyle_list for discovery or dimstyle_create if the style is missing, so it stops short of full when/when-not guidance.

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