bridge_edge_loops

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a geometry modification (creating faces) but does not clarify if the operation is destructive, what happens to the original edge loops, or how to undo it. For a simple operation, basic transparency is achieved, but there is room for more detail.

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 extremely concise: two sentences that cover the action and the essential prerequisite. Every sentence is meaningful and adds value. No wasted words.

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?

Despite the tool's simplicity, the description lacks information about return values or success/failure feedback. Combined with an undocumented parameter, the agent has incomplete context to use the tool effectively. Output schema is absent, so the description should at least hint at what the tool returns.

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 one required parameter 'name' with no description, and the tool description does not explain its purpose. Schema description coverage is 0%, so the description must compensate but fails to do so. The agent cannot infer what 'name' refers to (e.g., object name, mesh name).

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 clearly states the action ('Bridge'), the resource ('two selected edge loops'), and the result ('create connecting faces'). It effectively distinguishes from sibling tools like 'extrude_faces' or 'bevel_edges' by specifying the exact mesh topology operation.

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 a clear prerequisite: the object must have exactly two edge loops selected in edit mode. This tells the agent when to use the tool. However, it does not explicitly mention when not to use it or suggest alternative tools for different selection scenarios, which would be helpful.

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