rhino_create_point

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

The description contains only 'Create a point object in Rhino.' It does not disclose any behavioral details beyond the creation itself, such as whether it affects the current document, units, coordinate system, or if it overwrites an existing object. Annotations are all false (readOnlyHint, destructiveHint, etc.), providing no safety profile. With no annotation support, the description carries the full burden and fails to provide any meaningful behavioral context.

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 short sentence, which is efficient in length, but it is under-specified. It does not front-load any distinguishing or actionable information beyond the basic purpose. While there is no bloat, the brevity comes at the expense of clarity and completeness, so it is not appropriately conciseness – it is minimalism without substance.

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?

Given the tool's complexity (simple point creation) and the presence of an output schema (which may describe the return), the description is somewhat minimal. However, the lack of distinction from rhino_create_points and the absence of any usage guidance make it incomplete for an agent to correctly select and invoke it among many similar create tools. The description fails to capture context such as coordinate system or units, which could be relevant.

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 description does not mention any parameters at all. The schema itself documents each param (name, layer, point with x/y/z) with descriptions, but the schema description coverage signal is 0%, indicating the tool description explains none of the parameters. Since coverage is low, the description must compensate, but it does not add any meaning beyond what the schema already provides. This is a complete miss.

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 states a specific verb ('Create') and resource ('point object'), and it identifies the resource as a single point. However, it does not distinguish this tool from the sibling rhino_create_points (plural), which likely creates multiple points, nor from other create tools like rhino_create_line. The phrasing 'a point' hints at singular, but without explicit differentiation, an agent could confuse it with the plural variant.

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 such as rhino_create_points or other geometry creation tools. The description offers no conditions, exclusions, or references to sibling tools, leaving the agent to infer usage based solely on the name.

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