gh_connect_many

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

Beyond the minimal readOnlyHint=false annotation, the description discloses meaningful behavior: it returns a per-row results array, surfaces partial failures, and defines the status/error fields on each row. This clarifies the non-atomic failure mode, which is the critical behavioral trait for an agent invoking a batch write. It doesn't describe side effects on the GH document, but the core failure semantics are well covered.

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?

Two short sentences that front-load the purpose and add only the essential failure-semantics detail. There is slight internal redundancy ('per-row results array' followed by 'each row carries status and error'), but overall every sentence earns its place and the structure is clean.

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 rich input schema covers the connections array and stop_on_error structure, and the output schema covers the return shape, so the description rightly focuses on the missing piece: partial-failure behavior. For a batch tool this is nearly complete, though it omits any hint of prerequisites such as needing an open GH document or guidance on batching limits.

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?

With 0% schema description coverage at the top level, the description should compensate by explaining the connections batch and stop_on_error parameters, but it mentions neither. The nested $defs do carry individual property descriptions, which partially mitigates the gap, yet the description itself adds no parameter-level 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 uses a specific verb ('Add') with a clear resource ('multiple wires') and adds the 'single round-trip' batching context, which inherently distinguishes it from single-connection tools like gh_connect_components. However, it never names the sibling explicitly, so the differentiation is implied rather than stated.

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 implies a batch use-case through 'multiple wires' and 'single round-trip', giving an agent a reasonable sense of when to call it. But it provides no explicit guidance about when not to use it, no prerequisites, and no named alternative such as gh_connect_components.

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