merge_manager_work

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

No annotations are provided, so the description carries full burden. It discloses an access restriction ('Executive only') but fails to mention if the merge is destructive, conflict handling, or branch deletion behavior (though deleteBranch parameter exists). The description lacks critical behavioral traits for a merge tool.

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 sentence that conveys the core purpose efficiently. While it could include more context, it is not verbose and is front-loaded with the action. Slightly under-specified but still concise.

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 4 parameters (including an enum and a boolean) and no output schema, the description is too minimal. It omits return value, error cases, default behaviors (e.g., default targetBranch is 'main'), and any post-merge state. Incomplete for safe usage.

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 baseline 3. The description does not add any additional meaning beyond what the schema already provides for parameters like managerId, targetBranch, strategy, or deleteBranch. No elaboration on enum values or parameter impact.

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 ('Coordinate merge'), the resource ('manager work back to main branch'), and adds a restriction ('Executive only'). It distinguishes itself from siblings like commit_manager_work and sync_manager_branch.

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 mentions 'Executive only' as a usage restriction but provides no guidance on when to use this tool vs alternatives like commit_manager_work or sync_manager_branch. No explicit when-to-use or when-not-to-use context.

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