request_thread_merge

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

Beyond the annotations, the description discloses that this only creates a pending action and never executes a merge, that approval happens out-of-band via authenticated REST, and that the target state is kept while the source and its history are retained. These claims are consistent with readOnlyHint=false and destructiveHint=false, and they explain the real safety model rather than contradicting it.

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 pending-approval constraint is front-loaded in the first line, and each following sentence carries a distinct rule. There is mild redundancy between 'never executes a merge' and 'A human must review both states and approve,' but nothing is wasted overall.

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 an output schema present, the description need not explain return values, and annotations plus full schema coverage handle safety and parameter detail. The description supplies the remaining essentials: the approval workflow, retention behavior, and the forge-backed restriction.

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% and both parameter descriptions already state the retain-vs-keep semantics and the forge-backed restriction. The description's 'target state is kept, source and history retained' and 'forge-backed threads cannot be merged' largely restate the schema, adding no new syntax, format, or edge-case guidance.

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 opens with a specific verb and resource: 'Queue a local duplicate-thread merge for explicit human approval.' The words 'queue' and 'local' immediately distinguish it from an executing merge tool and from siblings such as suggest_duplicate_threads or thread_merge_history.

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?

It gives clear preconditions and constraints: the threads must be duplicates, forge-backed threads cannot be merged, and the human must approve through authenticated REST pending-actions. It never names the alternative tools (suggest_duplicate_threads, check_overlap) that an agent might choose instead, so it falls short of a full when/when-not routing statement.

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