rhino_add_dimension_ordinate

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

With no annotations to indicate safety or side effects, the description carries full burden. It only mentions entering a mode, without disclosing whether this creates objects, modifies the document, or requires user interaction. No behavioral implications are explained.

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, focused sentence with no unnecessary words. It is exceptionally concise and well-structured.

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?

The description provides only a minimal phrase without context about the mode's purpose, duration, or what happens after entering it. It lacks crucial operational details that a user or agent would need to understand the tool's function fully.

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, so the baseline of 4 applies. The description does not need to explain parameters because they do not exist.

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 (enter placement mode) and the object (ordinate dimension), which is specific enough. However, it lacks the additional clarity of naming the resource type explicitly (e.g., 'dimension') and could be more explicit about what 'mode' entails, so it is not a perfect 5.

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 provided on when to use this tool versus alternatives like rhino_add_dimension_linear or rhino_add_dimension_angular. The agent is left without context to choose this tool appropriately.

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