rhino_mesh_from_brep

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

The description reveals minimal behavioral traits beyond the annotation readOnlyHint=false. It confirms a write operation ('Mesh') but does not describe side effects like whether the mesh replaces the Brep or creates a new object, nor details about mesh quality or coordinate system. The 'bridge only' restriction is vague.

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 concise but to the point of being insufficient. It lacks structure or front-loading of important information; every word is necessary but the overall content is too sparse for effective tool use.

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 has 5 parameters with no schema descriptions and an output schema, the description is extremely incomplete. It does not mention required vs optional parameters, return values, or how the quality parameter affects results. The 'bridge only' constraint raises more questions than it answers.

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 input schema has 0% description coverage (params like 'object_id', 'quality', 'doc_id' lack definitions in the schema), and the description provides no explanation of any parameter. The agent receives no semantic help for filling in the required 'object_id' or optional 'quality' value.

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 the verb 'Mesh' and resource 'Brep', clearly indicating the tool converts a Brep to a mesh. The phrase '(bridge only)' adds a constraint but lacks clarity about what 'bridge' means. It distinguishes from similar sibling tools like 'rhino_mesh_from_surface' by specifying the source type, though 'bridge' remains ambiguous.

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 provides no explicit guidance on when to use this tool versus other mesh-creation tools. It only mentions 'bridge only', which suggests a specific context but does not explain when that context applies or exclude alternatives. No criteria for selection are given.

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