poly_connect_edges

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

Annotations already declare readOnlyHint=false and destructiveHint=true. The description adds that new edges are inserted, but does not disclose additional behavioral constraints such as edge adjacency requirements, permanence, or effects on surrounding topology. No contradiction with annotations.

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?

Tight and front-loaded, with the operation described first and use cases second. The bilingual duplication is the only minor redundancy, but each language block is compact and purposeful.

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?

All parameters are documented, the operation is clear, and the destructive annotation covers the risk profile. It leaves out edge-selection constraints and return behavior, but these are not essential for invoking this straightforward poly-editing tool.

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 coverage is 100%, so all parameters are already documented structurally. The description restates that segments controls the number of inserted edges and that edges are the connect target, but does not add meaning beyond the schema.

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?

States a precise verb (connect/insert), the resource (edges), and the controlling parameter (segments). It also clarifies the operation happens between selected edges, which distinguishes it from edge siblings like extrude or chamfer.

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?

Explicitly gives intended use cases: densify the mesh or add support loops. It does not name alternatives or exclusion cases, but the context is clear enough for an agent to decide when to use it.

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