rhino_offset_mesh

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds the useful detail that offsetting happens 'along face normals,' but it does not state whether the operation creates a new mesh, modifies the existing one, requires a selection, or how positive/negative distances behave. Important side-effect information is missing.

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 short and front-loaded, with the core operation stated in the first sentence. The Args block is mostly useful, though the controller line adds slight noise since that parameter is not present in the schema. Overall, it is economical.

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?

For a geometry-mutating tool with no annotations and no schema-level descriptions, this is underspecified. An agent cannot tell whether face selection is mandatory, how to perform the selection, what the resulting object is, or what failure conditions look like. The presence of an output schema reduces the need to document return values, but the operational gaps remain significant.

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 provides only a bare 'distance' integer with a default, so the description adds meaning by clarifying that the offset is along face normals. However, it does not explain units, sign convention, or the fact that the docstring mentions a 'controller' argument that is absent from the input schema, which may confuse an agent.

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 and resource: 'Offset selected mesh faces by a given distance.' This makes the tool's purpose immediately obvious and distinguishes it from sibling offset tools like rhino_offset_surface, rhino_offset_curve, and rhino_offset_subd.

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 phrase 'selected mesh faces' implies that the user must have a selection before calling, but the description gives no explicit when-to-use guidance and does not mention alternatives or exclusion conditions. An agent must infer the usage context from the tool name and sibling list rather than from the description.

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