rhino_dimension_aligned

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

The annotation readOnlyHint:false already signals a write operation, and the description's 'Add' is consistent. No additional transparency about side effects or required document state is provided, but there is no contradiction.

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, direct sentence with no unnecessary words. It efficiently conveys the tool's function without 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?

While the output schema exists (so return values need not be described), the description lacks contextual details such as typical use cases or differences from sibling dimension tools. It is adequate but not comprehensive for a tool in a large API family.

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 schema has one required parameter with 0% description coverage. The description text does not explain what the parameter represents (likely an input structure with geometry data), leaving the model without any semantic guidance for the argument.

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 the action ('Add') and the resource ('aligned dimension between two points'), which distinguishes it from sibling dimension tools like linear or angular. The purpose is immediately unambiguous.

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_dimension_linear or rhino_dimension_angular. The description only states what it does, leaving selection criteria to the model.

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