Connect Branch

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation (creating an edge) but says nothing about permissions, whether the edge is validated against the branch graph, idempotency, or what 'unconditional' means operationally. Only a faint hint is given.

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?

It is a single short line with no padding and the key qualifier front-loaded, which is structurally fine. It is arguably over-terse rather than concise, but there is no wasted text.

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?

With no annotations, no output schema, 0% parameter coverage, and three similarly-named siblings, the description leaves the agent without enough to invoke the tool confidently. It should at minimum explain what distinguishes an 'unconditional' edge from the conditional path and what the parameters mean.

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 0% across three parameters (from_id, to_id, project_id), and the description adds no semantics for any of them. The 'edge/connection' framing loosely implies from/to endpoints are the two node ids, but their format, directionality, and the optional project_id are undocumented everywhere.

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 Chinese description states a specific verb and resource ('connect branch graph edge'), which is more than a tautology of the name. However, it does not distinguish itself from the very similar sibling tools connect_nodes and add_branch_edge, so an agent cannot tell which of the three to pick from the description alone.

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 parenthetical '(unconditional shortcut)' hints that this variant skips conditions, but there is no explicit statement of when to use this rather than add_branch_edge or connect_nodes, nor any prerequisites or exclusions. Usage must be inferred.

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