blender_mesh_bridge

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 implies an in-place topology modification by stating it creates connecting faces, but it does not disclose prerequisites such as whether both loops must belong to the same object, matching loop sizes, or how invalid selections behave.

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 sentence with the core action front-loaded, followed by three concise, relevant use cases. Every phrase earns its place and there is no redundancy or filler.

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?

The description covers the core purpose well but leaves out important operational context for an unannotated mesh-modification tool: expected return value, prerequisites for valid edge loops, and failure behavior. Since there is no output schema or annotations, this gap is noticeable but not fatal.

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 100%, so the input schema already documents every parameter, including twist, segments, profile_factor, and the edge loop arrays. The tool description adds no parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Bridge two edge loops to create connecting faces,' which clearly states the operation and result. It also gives concrete use cases like connecting body panels and creating tubes, which help distinguish it from similar mesh tools such as fill or merge.

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 clear contextual use cases: connect body panels, create tubes between openings, join separate mesh islands. It does not explicitly mention when not to use it or name alternatives, but the examples strongly signal appropriate scenarios.

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