REVIEW 5 major objections 4 minor 5 cited by
A constraint-aware LLM agent grounded in a structured database of over 150 remote sensing models can recommend the right foundation model for a given task and user constraints, outperforming retrieval-only, unstructured RAG, and naive agent
Reviewed by Pith at T0; open to challenge. T0 means a machine referee read the full paper against a public rubric. the ladder, T0–T4 →
T0 review · deepseek-v4-flash
2026-08-03 20:55 UTC pith:HVDYOMVR
load-bearing objection The RS-FMD database and the REMSA agent are a real contribution worth refereeing, but the evaluation is a proxy with an abstract/body mismatch and an overclaimed summary that the paper's own Table 2 contradicts. the 5 major comments →
REMSA: Foundation Model Selection for Remote Sensing via a Constraint-Aware Agent
The pith
A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.
Core claim
The paper's central claim: a constraint-aware LLM agent grounded in a structured database selects better remote sensing foundation models than retrieval-only, unstructured RAG, or naive agent baselines. REMSA parses free-text queries into structured constraints, retrieves candidates by embedding similarity, filters hard-constraint violators, ranks survivors via in-context reasoning, asks clarifying questions when needed, and explains its output. RS-FMD stores 150+ models in a schema covering modalities, sensors, resolution, pretraining data, and benchmarks. On 75 expert-scored queries, REMSA posts the best average expert scores (75.76 top-1, 75.03 set), best high-quality hit rate (40%), and
What carries the argument
The load-bearing mechanism is the structured schema of RS-FMD paired with REMSA's task-aware orchestration loop: dense retrieval over field-prefixed metadata for recall, deterministic filtering for hard constraints, in-context LLM ranking with few-shot examples, clarification rounds for missing fields, and explanation generation. The confidence-scored extraction pipeline (log-probability plus self-consistency) keeps the metadata reliable enough to filter on.
Load-bearing premise
The load-bearing premise is that two experts scoring each recommended model on seven rubric criteria—with weights set by the same team that built the system—is a valid proxy for how well that model would actually perform on the user's real task; no model is ever run on a real downstream task.
What would settle it
Take a held-out set of RS query scenarios, run each system's top-3 recommendations on the actual downstream task (e.g., fine-tune or zero-shot evaluate on a labeled segmentation or classification dataset), and compare true task performance against the expert rubric scores. If rubric rankings do not correlate with actual task performance, the evaluation claim collapses.
If this is right
- Practitioners can replace manual paper-and-model-card searching with a natural-language interface that returns ranked, explained recommendations in roughly 30 seconds per query.
- RS-FMD becomes a reusable community resource: once model metadata is structured, other tools—benchmarks, AutoML, or retrieval systems—can build on it without re-parsing papers.
- Under-specified queries no longer degrade selection quality, because the clarification loop asks for missing modality, compute budget, or region before ranking.
- The baseline comparisons imply the gain is from the orchestrated combination, not any single component: retrieval-only and unstructured RAG both underperform the full agent.
- Because REMSA is designed to be LLM-agnostic, improvements in underlying language models should transfer directly to better selection.
Where Pith is reading between the lines
- The expert rubric is never validated against actual task performance—no recommended model is run on a real downstream task—so a natural extension is a benchmark that fine-tunes or zero-shot evaluates the top recommendations and checks whether rubric scores predict task performance.
- The sensitivity analysis shows that dropping Efficiency or Popularity+Recency slightly improves REMSA's scores, suggesting the rubric's weights may penalize less famous but technically stronger models; re-weighting the rubric would be a testable change.
- The database is limited to models the authors could find, and the paper flags that rare or emerging use cases may be missing; the agent's robustness on out-of-coverage models is untested.
- Clarification rounds were simulated with an LLM during evaluation; a human-in-the-loop study could reveal whether real users' answers help or hurt the ranking.
Editorial analysis
A structured set of objections, weighed in public.
Referee Report
Summary. The paper introduces RS-FMD, a schema-guided database of roughly 150 remote sensing foundation models, and REMSA, an LLM agent that performs constraint-aware model selection from natural-language queries. REMSA combines structured metadata retrieval, rule-based filtering, in-context ranking, clarification rounds, explanation generation, and a task memory component. The authors construct a benchmark of 75 expert-verified queries and evaluate the top-3 recommendations of REMSA and three baselines (REMSA-NAIVE, DB-RETRIEVAL, UNSTRUCTURED-RAG) using expert scores on seven weighted criteria. The central claim is that REMSA consistently outperforms all baselines across all evaluation metrics, demonstrating effectiveness in selecting RSFMs under real-world constraints.
Significance. RS-FMD is a potentially valuable community resource, and the paper is transparent: the schema, prompts, benchmark templates, and evaluation appendices are all included, and code/data are promised at an open repository. If the evaluation is accepted, the paper would provide a useful framework for automated foundation-model selection, a topic of growing practical importance. However, the current evidence primarily demonstrates alignment with the authors' own rubric, not with actual downstream task performance. The methodological strengths — structured metadata, full prompt disclosure, reproducibility of the pipeline — are real, but the central comparative claim is weakened by missing statistical rigor and the lack of any validation against real task outcomes.
major comments (5)
- [§6.1, Table 2] The claim that REMSA 'consistently outperforms all baselines in all evaluation metrics' is contradicted by Table 2 itself: REMSA's Top-1 Hit Rate (22.67%) is lower than REMSA-NAIVE's (25.33%). The text later acknowledges this, but the §6.1 opening overstates the result. In addition, all metrics are single-point scores from stochastic LLM systems, with no significance tests, confidence intervals, or run-to-run variance reported; the 3.09-point Avg Top-1 gap over REMSA-NAIVE and 0.02 MRR gap may be within noise. Please report paired statistics across the 75 queries (e.g., bootstrap CIs, Wilcoxon signed-rank test) or multiple seeds/temperatures.
- [§5, App. G/I] The evaluation measures expert scores on a rubric authored by the same team, not whether the recommended model actually performs well on the user's task. No recommended FM is run on a downstream task, and the paper itself calls the protocol a 'proxy' (§5). Because the ranking prompt (App. D) explicitly instructs the LLM to prioritize application, modality, min_performance, efficiency, and benchmark diversity — exactly the dimensions that dominate the rubric (weights 25/20/20/15/10/5/5 in App. I) — REMSA is in effect optimized to maximize the score function by which it is later judged. The comparison is therefore largely about alignment with the authors' criteria. To support the practical-utility claim, I ask for a small downstream validation (e.g., fine-tune or evaluate a handful of top-1 recommendations on held-out tasks) or at least evidence that expert scores correlate with actual tas
- [§6.2, Table 3] The sensitivity analysis shows that removing Efficiency or Popularity+Recency from the scoring rubric increases Avg Set Top-1 (80.23 and 75.13 vs. 75.03) and Top-1 Hit Rate (25.33% both vs. 22.67%). This suggests that these criteria penalize systems under the remaining rubric, which is in tension with the §6.2 claim that REMSA 'does not overfit to superficial indicators.' At minimum, the finding indicates that the full scoring rubric is not neutral with respect to the intended deployment trade-offs. Please reconcile this and discuss whether the 15/5/5 weights are appropriate.
- [Abstract vs. Main Text] The abstract states 'a benchmark of 100 expert-verified RS query scenarios... 3,000 expert-scored task–system–model configurations,' while the main-text abstract and §5 report 75 queries and 900 configurations. This numerical inconsistency must be corrected.
- [§5, §4.1] All clarification rounds in REMSA were executed automatically, with an independent LLM simulating user responses. The neutrality of this simulation is not established: the prompt used to simulate the user is not given, and if the simulated user cooperatively supplies the missing constraints in a form that matches the parser's schema, the clarification loop can only improve REMSA's results. Please provide the simulation prompt and an analysis of sensitivity to user behavior, or run a subset with real users.
minor comments (4)
- [§6 Metrics] The metric name 'Mean Reciprocal Rank' is abbreviated as MMR in the text; the standard abbreviation is MRR (and Table 2 uses MRR). Please correct.
- [§3] There is a typo 'aas' in the sentence 'occasional field-level errors have limited impact on FM selection aas the most decisive properties...'.
- [References] The same VisualAgentBench citation appears twice as Liu et al., 2025a and 2025b with identical bibliographic details; if these are intended to be the same paper, one should be removed.
- [App. B] The query-schema template contains a typo: 'avaliable_data' should be 'available_data'.
Circularity Check
No significant circularity: REMSA's evaluation is a self-admitted proxy; prompt-rubric overlap is design intent, not a construction-level reduction.
full rationale
The claimed derivation chain is not circular. RS-FMD is independently assembled from public metadata; REMSA's in-context ranking prompt (Appendix D) is a design input, not a fitted parameter. The paper nowhere equates the prompt's heuristics with the expert score: the rubric (Table 1, Appendix I) weights Application 25%, Modality 20%, Reported Performance 20%, Efficiency 15%, Generalizability 10%, Popularity 5%, Recency 5%, whereas the prompt instructs the LLM to prioritize hard constraints then efficiency/diversity, and omits popularity/recency as primary drivers. The system never sees the rubric or the weights during inference, and experts score blindly and independently (Appendix G), so the measured result is not forced by construction. Section 5 explicitly calls the protocol 'a reproducible and practical proxy', correctly bounding the claim to expert-judged suitability rather than downstream task performance. The confidence weights (Eq. 1) are tuned on a 10-record validation set; orchestration thresholds are 'empirically determined' - neither is a prediction from the benchmark. Table 3 also shows REMSA is not simply maximizing the rubric (dropping Efficiency or Popularity+Recency improves scores). There are no load-bearing self-citations or imported uniqueness theorems. Two reporting/correctness caveats are not circularity: (i) Section 6.1's 'consistently outperforms ... in all evaluation metrics' is contradicted by Table 2, where REMSA's Top-1 Hit Rate (22.67%) is below REMSA-NAIVE (25.33%); (ii) the benchmark queries are template-generated by the same team and no holdout statement covers prompt/few-shot/threshold development, leaving external validity dependent on the acknowledged proxy assumption.
Axiom & Free-Parameter Ledger
free parameters (7)
- Confidence score weights in Eq. 1 =
w_logp = 0.7, w_cons = 0.3
- Confidence flag threshold theta =
0.75
- Sigmoid temperature tau for log-prob normalization =
0.5
- Expert scoring weights (7 criteria) =
25/20/20/15/10/5/5
- Orchestration thresholds (ranking confidence, constraint coverage, clarification rounds) =
not specified
- FAISS retrieval similarity threshold =
not specified
- MaxCandidates threshold in Algorithm 1 =
not specified
axioms (4)
- domain assumption LLM-based schema-guided extraction yields metadata accurate enough for FM selection
- domain assumption Expert rubric scores are a valid proxy for real FM suitability
- domain assumption In-context ranking with a few expert-crafted examples is sufficient without supervised training
- domain assumption GPT-4.1 (or a swap-in LLM) reliably parses constraints and ranks candidates
read the original abstract
Foundation Models (FMs) are increasingly integrated into remote sensing (RS) pipelines. These models include unimodal vision encoders and multimodal architectures. FMs are adapted to diverse perception tasks, such as image classification, change detection, and visual question answering. However, selecting the most suitable remote sensing foundation model (RSFM) for a specific task remains challenging due to scattered documentation, heterogeneous formats, and complex deployment constraints. To address this, we first introduce the RSFM Database (RS-FMD), the first structured and schema-guided resource covering over 160 RSFMs trained on various data modalities, spanning different spatial, spectral, and temporal resolutions, considering different learning paradigms. Built upon RS-FMD, we further present REMSA, a constraint-aware agent that enables automated RSFM selection from natural language queries. REMSA combines structured FM metadata retrieval with a task-driven decision workflow. In detail, it interprets user input, clarifies missing constraints, ranks models via in-context learning, and provides transparent justifications. Our system supports various RS tasks and data modalities, enabling personalized, reproducible, and efficient FM selection. To evaluate REMSA, we construct a benchmark of 100 expert-verified RS query scenarios. Each query is evaluated across 4 systems and 3 LLM backbones, with the top-3 selected models manually assessed by domain experts. This results in 3,000 expert-scored task--system--model configurations under our novel expert-centered evaluation protocol. REMSA outperforms multiple baselines, showing its practical utility in real decision-making applications. REMSA operates entirely on publicly available metadata of open source RSFMs, without accessing private or sensitive data.
Figures
Forward citations
Cited by 5 Pith papers
-
GeoAgentBench: A Dynamic Execution Benchmark for Tool-Augmented Agents in Spatial Analysis
GeoAgentBench supplies a live execution environment and Plan-and-React architecture that lets tool-using AI agents handle multi-step GIS tasks more robustly than prior static evaluation methods.
-
Multimodal Large Language Models for Remote Sensing Image Understanding: Domain-Specific or General-Purpose?
Under one zero-shot protocol, general-purpose MLLMs match or outperform remote-sensing-specific MLLMs on several RS benchmarks, while RS-MLLMs keep advantages in visual grounding, RS-VQA, and ultra-high-resolution und...
-
Agentic AI for Remote Sensing: Technical Challenges and Research Directions
Agentic AI faces structural challenges in remote sensing due to geospatial data properties and workflow constraints, requiring EO-native agents built around structured state, tool-aware reasoning, and validity-aware e...
-
Agentic AI for Remote Sensing: Technical Challenges and Research Directions
Agentic AI for remote sensing requires new designs centered on structured geospatial state, tool-aware reasoning, verifier-guided execution, and physical validity rather than generic extensions.
-
Agentic AI for Remote Sensing: Technical Challenges and Research Directions
Position paper identifies structural challenges in applying generic agentic AI to Earth Observation and outlines design principles for EO-native agents focused on geospatial state and validity.
Reference graph
Works this paper leans on
-
[1]
A structured user query specifying task requirements and constraints
-
[2]
application
A list of candidate models retrieved from a database, each with metadata fields. Your goal: - Rank the candidate models from most to least suitable for the user’s query. - For each model, provide a brief explanation in several bullet points describing why it is placed at that rank. - Prioritize hard constraints (application, modality, required sensor, and...
-
[3]
CACo Ranking Output:
-
[5]
S2MAE - Directly supports Sentinel-2 multispectral data - Achieves 99.1\% accuracy on EuroSAT, exceeding 85\% requirement - Purpose-built for land cover classification
-
[6]
Prithvi - Supports multi-temporal multispectral data, including Sentinel-2 - Accuracy slightly below requirement on similar tasks - More generalist FM
-
[7]
model": <model_name>,
CACo - Only supports RGB modality - Accuracy below the 85\% requirement - Designed mainly for change detection and event retrieval Your Task: 20 Given the following new query and candidates, produce a ranked list with explanations. Structured Query: {query} Candidate Models: {candidates} Please output the ranked list as JSON in the following format: [ { "...
-
[8]
model_name
For each model, output a JSON object with: - "model_name" - "explanation" (several bullet points on why it is recommended) - "paper_link" - "repository"
-
[9]
Highlight how the model satisfies or partially satisfies the query
-
[10]
efficiency, modality coverage, etc.)
Mention key trade-offs if relevant (accuracy vs. efficiency, modality coverage, etc.). F. PROMPT FORRAG-LLM BASELINE For the LLM-RAG baseline, we prompt an LLM with the original user input and the retrieved model documentation as a context. The LLM is instructed to select and rank the top three remote sensing foundation models and provide concise explanat...
-
[11]
Select and rank the top 3 remote sensing foundation models most suitable for the task
-
[12]
-- The reason for its ranking position compared to others
For each selected model, provide: -- A short explanation of why it fits the task requirements. -- The reason for its ranking position compared to others. -- Any other relevant information from the context
-
[13]
Follow this exact output format:
-
[15]
model: <model_name> explanation: - <reason 1> - <reason 2> - <reason 3>
-
[16]
EXPERTEVALUATIONPROCEDURE Expert Background.All annotations were performed by two experts with a computer science background and specialization in RS
model: <model_name> explanation: - <reason 1> - <reason 2> - <reason 3> G. EXPERTEVALUATIONPROCEDURE Expert Background.All annotations were performed by two experts with a computer science background and specialization in RS. Both have prior experience working with RSFMs, have published in the relevant domains, and are familiar with model architectures, p...
-
[17]
Geographic diversity: global (score 5), multi-regional (3–4), or single-region coverage (1–2)
-
[18]
Sensor-modality diversity: number of distinct modalities used in pretraining e.g., optical, SAR, multi- spectral, hyperspectral)
-
[19]
These components were combined into a composite 1-5 score
Dataset scale: reported total area, number of scenes, or total images. These components were combined into a composite 1-5 score. Inter-annotator agreement confirmed that the rule-based definitions reduced subjectivity. • Recency. Recency was defined by the publication year or the latest model-card update: 2025–2026= 5,2024 = 4,2023 = 3,2022 = 2, . . . Gi...
2025
-
[2023]
OpenReview.net, 2023. 13 APPENDIX A. COMPLETERS-FMDSCHEMASPECIFICATION To properly represent the properties of each FM, we designed a comprehensive data schema forRS-FMD. The schema includes the essential characteristics of model architectures, pretraining strategies, supported modalities, and benchmark performance. Each model record includes fields such ...
Pith/arXiv arXiv 2023
discussion (0)
Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.