rhino_validate_brep

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

Annotations already mark the tool as readOnlyHint=true, so the description does not need to re-state safety. It adds useful behavioral detail beyond annotations: standalone mode returns IsValid/IsSolid/IsManifold, counts, and a validation log, while bridge mode adds naked-edge identifiers and lengths. The only notable gap is that 'Bridge mode' is not defined in terms of inputs or environment.

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 appropriately concise and front-loaded with the main purpose. The second sentence adds valuable detail, though the indentation and unexplained 'Bridge mode' phrase add minor ambiguity. Overall, every sentence contributes.

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?

An output schema exists, so return values are already documented elsewhere, and the readOnlyHint annotation covers mutation concerns. However, the tool has at least one important ambiguity—what triggers bridge mode and how it changes validation—and no guidance on selecting this tool over related validation/checking tools. This is adequate but not fully complete.

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 reported as 0%, and the description does not explain the parameters or how doc_id/object_id affect behavior. The mention of 'Standalone' vs 'Bridge mode' is relevant to behavior but is not mapped to a parameter, leaving the agent without enough information about how to select a mode.

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 opens with a specific verb and resource: 'Validate a Brep', followed by the key validation dimensions (closed/solid/manifold, face/edge counts, issue log). This clearly identifies the tool's function, though it does not explicitly differentiate it from nearby validation tools like rhino_check_naked_edges or rhino_check_bad_objects.

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 does not state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. It implies a validation use case but leaves the agent to infer when this is the right choice among many similar geometry-analysis tools.

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