rhino_dimension_aligned

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

The description 'Add' aligns with readOnlyHint=false (mutation). However, it adds no additional context beyond the annotation; no mention of side effects, document requirement, or return behavior. Minimal but consistent.

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?

Single sentence, no wasted words, information is front-loaded. Appropriate for a simple concept, though overly minimal for the 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?

Despite output schema existing, the description is too terse given the nested input schema and many sibling dimension tools. Fails to explain the coordinate system, plane requirement, or return value, leaving significant gaps.

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?

With 0% schema description coverage, the description must compensate. It only hints at 'two points' but ignores other parameters (name, layer, plane, doc_id). Does not explain the role of the plane or how coordinates are interpreted.

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?

Description uses specific verb 'Add' and resource 'aligned dimension', and mentions 'between two points', which clearly indicates the tool's function and distinguishes it from sibling tools like rhino_dimension_linear (horizontal/vertical) and rhino_dimension_angular.

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 on when to use this tool vs alternatives (e.g., rhino_dimension_linear, rhino_dimension_angular). No mention of prerequisites or context where aligned dimension is appropriate.

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