ecosystem_merge_main

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

No annotations are provided, so the description carries the transparency burden. It discloses that conflicts are reported and that either target_branch or the current branch is used, which adds behavioral context. However, it does not mention potential side effects such as file modifications, uncommitted changes, or the need for a clean working tree, which are important for a merge operation.

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 concise sentence that front-loads the action and includes essential qualifiers (branch choice and conflict reporting). It is appropriately sized with no wasted words, making it easy for an agent to parse quickly.

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?

Given no output schema and no annotations, the description reasonably covers the main purpose, the branch selection logic, and the conflict reporting outcome. It is missing details about the merge's side effects (e.g., working tree changes, commit behavior) and prerequisites, but for a simple merge tool, the description is sufficiently complete for basic selection and invocation.

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 only a parameter name and default null with no description, giving 0% schema coverage. The description compensates by explaining that target_branch specifies the ecosystem branch and if it is not provided, the current branch is used. This adds meaningful semantics beyond the schema, though it could be more explicit about the format or null behavior.

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 identifies the action ('mergea main' = merge main) and the target resource (the ecosystem branch, either target_branch or current branch). This distinguishes it from sibling tools like ecosystem_branch_create or ecosystem_sync_upstream, making the tool's specific function immediately obvious.

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 when to use this tool (when merging main into an ecosystem branch) but does not explicitly mention alternatives or exclusions. It lacks a clear 'when not to use' or comparison with siblings like ecosystem_sync_upstream, leaving usage guidance mostly implied.

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