rhino_mesh_from_brep

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

readOnlyHint=false already signals mutation, and the description adds little behavioral context. It does not state whether a new mesh object is created, whether the source Brep is altered, what layers or names are used, or what 'bridge only' actually means.

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 text is short and front-loaded, but this is under-specification rather than effective conciseness. The unexplained parenthetical '(bridge only)' is not informative, and essential behavioral and usage context is absent.

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 conversion tool with multiple input fields and no meaningful parameter documentation, a single sentence is inadequate. It omits how the Brep is selected, what quality controls, and what side effects or outputs to expect; the output schema does not compensate for the missing input and behavior context.

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 description coverage is 0%, and the description names none of the schema parameters. It does not explain that object_id must reference a Brep or how quality, layer, name, and doc_id affect the result, so it fails to compensate for the missing schema descriptions.

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 has a specific verb ('Mesh') and resource ('a Brep'), so the core operation is identifiable and is reinforced by the title. It partially distinguishes from siblings like rhino_mesh_from_surface and rhino_mesh_from_nurbs by naming Brep as the input type, though the parenthetical '(bridge only)' is cryptic and adds ambiguity.

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 when-to-use guidance, exclusions, or alternative tools are mentioned. An agent cannot tell from the description whether to choose this over rhino_mesh_from_surface or rhino_mesh_from_nurbs, or what conditions make this tool appropriate.

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