Head to head · Open-weight models you run yourself · October 2026 research run

OTel-2.0-LLM-31B-IT vs Qwen3.5-9B

Qwen3.5-9B scores 60.5 (C) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 2 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on documentation and upkeep. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

Which one, for what

OTel-2.0-LLM-31B-IT C

Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware

Ahead on

  • Documentation and upkeep, 74 against 34

Watch for

BF16 only at 62.6 GB, with no GGUF or other quantised build from anyone we checked

Qwen3.5-9B C

Best for Agents that want a small multimodal tool-calling model on a laptop or a 16 GB GPU, under a plain licence

Ahead on

  • Reach, 85 against 50
  • Agent interface, 70 against 60

Watch for

No quantised build from Qwen itself

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep OTel-2.0-LLM-31B-IT +40

OTel-2.0-LLM-31B-IT 74

Model card 14, Intended use, a long limitations section, the architecture and training method, the parameters (31B) and the language (English) are on the card. Training data 15, the card names the sources (3GPP, ETSI, ITU, GSMA, CAMARA, O-RAN and TM Forum material provided by GSMA), the overall sizes (15 billion raw tokens, over 1 trillion processed, about 440 billion used), the mix of example types and the processing tool, and lists what was left out. Last change 20, the last commit, on 1 November 2026, updated the card's links, resources, citation and contacts, nine days before this check. Responsiveness 20, Of the 3 discussions that aren't pull requests (7 August to 28 October 2026), 2 have a reply from the repository's owner, which is most. Version policy 0, the weights were replaced in place: uploads on 27 July, 3 August and 1 September 2026 under one name, with a standing notice on the card that they may change and that users should pin a revision, and no dated note of what changed. File health 5, the card describes 15 shards of about 62.6 GB while the repository still holds an earlier 14-shard set beside them, 126.8 GB in all. 14 + 15 + 20 + 20 + 0 + 5 = 74.

Qwen3.5-9B 34

Model card 14, it covers intended use, architecture, parameters, context and 201 languages but gives no limitations and no knowledge cut-off. Training data 5, a general line about trillions of multimodal tokens with no cut-off. Last change 5, the files and card last changed on 2 March 2026 (c202236), 247 days before 4 November, within a year. Responsiveness 0, no Qwen member replied in any of the 40 most recent of the 45 discussions that aren't pull requests (2 March to 29 September 2026). Version policy 5, a first release that was never replaced in place, with no dated notes across generations. File health 5, two reports about the files and card (15 and 51) are still open with no reply. 14 + 5 + 5 + 0 + 5 + 5 = 34. The card's highlights mention sparse Mixture-of-Experts for the series while this 9B is dense, but its own overview matches config.json, so it's not counted as a contradiction.

Reach Qwen3.5-9B +35

OTel-2.0-LLM-31B-IT 50

Memory 10, the publisher's only build is the BF16 safetensors, 62.55 GB for the 15 shards the index names, and 62.55 GB × 1.2 = 75.1 GB, above 64 GB and inside the reference machine's GPU share. Runtimes 15, the architecture is Gemma4ForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors files, three at 5 each. Builds 0, the publisher ships the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata, an OSI licence, with nothing added on the card. Download 10, gated is false on 10 November 2026, so the files download with no account or terms. Hosted 0, Hugging Face maps one inference provider, Featherless AI (live), short of the two the line needs. 10 + 15 + 0 + 15 + 10 + 0 = 50.

Qwen3.5-9B 85

Memory 30, Qwen publishes no quantised 9B, so the smallest 4-bit build from a runtime's own library is Ollama's qwen3.5:9b at 6.6 GB, about 7.9 GB with the fifth added, well under 16 GB. Runtimes 25, the cap, with vLLM listed in its stable docs, Transformers at released tags, llama.cpp, Ollama's library, LM Studio's own catalogue and SGLang all running the architecture. Builds 0, Qwen's FP8 and GPTQ repositories cover only the 27B and larger Qwen3.5 models, so every quantisation of the 9B is someone else's. Terms 15, plain Apache 2.0. Download 10, the repository isn't gated. Hosted 5, Together, Featherless AI, OVHcloud and DeepInfra are live for it on its Hugging Face page. 30 + 25 + 0 + 15 + 10 + 5 = 85.

Agent interface Qwen3.5-9B +10

OTel-2.0-LLM-31B-IT 60

Chat template 20, chat_template.jinja in the repository, 19,300 characters, the publisher's own. Tool-calling format 10, only the template says how tools are declared and how calls come back. Trained tool calling 20, the template loops over tool_calls, so it renders several calls in one turn, and the card says the training mix included general-purpose agentic tool-calling examples, while none were specific to telecoms. Structured output 0, the card doesn't document JSON or JSON Schema output. Reasoning control 0, the card says the model wasn't trained to produce or consume Gemma's thought channel and answers directly, so there is no thinking to switch or budget. Context 10, 262,144 positions in the text config, the base's native context. 20 + 10 + 20 + 0 + 0 + 10 = 60.

Qwen3.5-9B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10, the card names the qwen3_coder parser for vLLM and SGLang but leaves the declaration and return format to the template, and Qwen's own function-calling guide still describes Qwen3's Hermes format. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, nothing documents asking the weights for JSON. Reasoning control 10, thinking turns off per request with enable_thinking false and the reasoning comes back in think tags that the qwen3 parser splits out. Context 10, 262,144 tokens native.

Score by category

CategoryWeight this runOTel-2.0-LLM-31B-ITQwen3.5-9BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255085Qwen3.5-9B +35
Risk20%205555even
Agent interface10%106070Qwen3.5-9B +10
Documentation and upkeep10%107434OTel-2.0-LLM-31B-IT +40
Negative events≤1500
TotalC 56.8/100C 60.5/100

Facts side by side

FactOTel-2.0-LLM-31B-ITQwen3.5-9B
KindOpen-weight modelOpen-weight model
VendorAT&T (Open Telco AI)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-11-012026-03-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.5/5 (4)

Verdicts

OTel-2.0-LLM-31B-IT

A real telecoms post-training of Gemma 4 31B IT with an unusually candid card on what was and wasn't trained. It fits a 128 GB machine in BF16 only, with no quantised build, sits in a personal account, and its weights have been replaced in place. Tool-call format, structured output and safety results aren't documented.

Qwen3.5-9B

A small dense vision-language model with trained tool calling, thinking that turns off per request and a 262,144-token context. Ollama's 4-bit build is 6.6 GB and the BF16 files 19.3 GB, and every major runtime loads it. The files haven't changed since 2 March 2026, Qwen answered none of the 40 latest discussions, and no safety results are published.

Before you call either

OTel-2.0-LLM-31B-IT

  1. Download the 15 shards the index names, not the whole repository, which is twice the size
  2. Pin a revision. The card says the weights may change under the same name
  3. Serve it with vLLM 0.19.0 or later and the repository's own chat template, not Gemma 4's
  4. Send no thinking flags. It answers directly and wasn't trained on Gemma's thought channel
  5. Use it as the generation stage of a RAG pipeline over telecom standards, with source attribution and human review
  6. Don't use it to run network tools unattended. The card says that hasn't been evaluated

Qwen3.5-9B

  1. Smallest start is ollama run qwen3.5:9b (6.6 GB, q4_k_m)
  2. On vLLM run vllm serve Qwen/Qwen3.5-9B --port 8000 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, or tool calls come back as text
  3. Tool calls use the XML style <tool_call><function=name><parameter=x>, not Hermes JSON, so use the qwen3_coder parser and not hermes
  4. Thinking is on by default; pass chat_template_kwargs with enable_thinking false for short tasks, since /nothink isn't supported
  5. There's no generation_config.json, so pass sampling yourself, temperature 1.0, top_p 0.95, top_k 20, presence_penalty 1.5 when thinking, or 0.7, 0.8, 20, 1.5 without
  6. Keep at least 128K of context when thinking, and turn on YaRN only beyond 262,144 tokens
  7. Validate JSON output yourself or use the runtime's guided decoding

Questions

Which is better for AI agents, OTel-2.0-LLM-31B-IT or Qwen3.5-9B?

Qwen3.5-9B scores 60.5 (C) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 2 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on documentation and upkeep.

Other comparisons with OTel-2.0-LLM-31B-IT or Qwen3.5-9B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.