create_bearing_hole

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the action (create a hole) but does not mention whether it modifies existing geometry, requires a target body, or any side effects. Minimal transparency.

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?

Two sentences, front-loaded with the primary action. Every word is necessary; no filler. Highly 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 covers the core functionality but omits placement context (e.g., x, y, body_name, face_index) and hole depth. However, since the schema fully describes these parameters with 100% coverage, the description is adequate but could be improved by noting that a target body is required.

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%, baseline 3. The description adds value by explaining that bearing_number maps to JIS standard dimensions and that bore_diameter auto-selects a 6200 series bearing, which is not in the schema parameter descriptions. This provides meaningful context.

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 it creates a bearing bore hole sized to JIS B1520 standard dimensions, specifying a verb ('create') and a specific resource ('bearing bore hole'). It distinguishes from sibling tools like create_sketch or create_counterbore_hole by focusing on bearing dimensions.

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?

The description implies use for creating bearing holes with JIS standard sizes, but does not explicitly state when to use this over alternatives like create_counterbore_hole or create_countersink_hole. No exclusions or when-not-to-use guidance is provided.

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