/**
 * This module exports various prompts used for model graded evaluation.
 * They are imported and re-exported by the `prompts` module.
 *
 * @module prompts
 */
export * from './external/ragas';
export declare const DEFAULT_GRADING_PROMPT: string;
export declare const TRUSYS_FACTUALITY_PROMPT: string;
export declare const OPENAI_CLOSED_QA_PROMPT: string;
export declare const SUGGEST_PROMPTS_SYSTEM_MESSAGE: {
    role: string;
    content: string;
};
export declare const PLAN_ADHERENCE_PROMPT = "You are an evaluation assistant. Your job is to evaluate plans generated by AI agents to determine whether it will accomplish a given user task based on the available tools or agents.\n\nHere is the data:\n    [BEGIN DATA]\n    ************\n    [User task]: {{ task }}\n    ************\n    [Tools or Agent definitions]: {{ definitions }}\n    ************\n    [Plan]: {{ plan }}\n    [END DATA]\n\nDefinitions format: Either (1) a list of tools, each with \"name\", \"description\", and \"arguments\", or (2) a list of agent definitions, each with \"name\", \"description\", and \"tool_definitions\" (nested list of tools). Use whichever is provided to judge the plan.\n\nHere is the criteria for evaluation\n1. Does the plan include only valid and applicable tools/agents for the task?\n2. Are the tools/agents used in the plan sufficient to accomplish the task?\n3. Will the plan, as outlined, successfully achieve the desired outcome?\n4. Is this the shortest and most efficient plan to accomplish the task?\n\nRespond with a JSON object containing exactly two fields:\n- \"result\": one of \"ideal\", \"valid\", or \"invalid\"\n- \"reason\": a brief explanation for your evaluation\n\n\"ideal\" means the plan generated is valid, uses only available tools/agents, is the shortest possible plan, and will likely accomplish the task.\n\n\"valid\" means the plan generated is valid and uses only available tools/agents, but has doubts on whether it can successfully accomplish the task.\n\n\"invalid\" means the plan generated includes invalid steps that cannot be used based on the available tools/agents.\n\nYour response must be valid JSON only, with no other text or characters.";
/** Evaluates how well the agent's tool_calls or agent_calls adhered to the stated plan. */
export declare const PLAN_ADHERENCE_EVAL_PROMPT = "You are an evaluation assistant. Your job is to evaluate how well an AI agent's actual execution (tool calls or agent calls) adhered to its stated plan for a given user task.\n\nHere is the data:\n    [BEGIN DATA]\n    ************\n    [User task]: {{ task }}\n    ************\n    [Plan]: {{ plan }}\n    ************\n    [Actual tool calls or agent calls]: {{ trace }}\n    [END DATA]\n\nTrace format: Either (1) a list of tool calls, each with \"name\", \"description\", \"arguments\", and optionally \"output\", or (2) a list of agent calls, each with \"name\", \"description\", and \"tool_calls\" (nested list of tool calls). Use whichever is provided to compare against the plan.\n\nCompare the plan to the trace. Then assign exactly one adherence level.\n\nRespond with a JSON object containing exactly two fields:\n- \"result\": one of \"perfect\", \"strong\", \"partial\", \"weak\", or \"none\"\n- \"reason\": a brief explanation for your evaluation\n\nScoring criteria (use exactly these labels):\n\n**1.0 \u2014 perfect**: Every planned step is explicitly and verifiably present in the trace, in correct order. No skipped or added steps. No ambiguity in matching.\n\n**0.75 \u2014 strong**: All or nearly all steps are executed in order. At most one minor deviation (e.g., a trivial reordering or minor redundant step) that does not change the plan's structure.\n\n**0.5 \u2014 partial**: Some steps clearly match, but others are missing, out of order, or replaced. At least one extra or ambiguous action appears. This is the highest score possible when there are any deviations.\n\n**0.25 \u2014 weak**: Only a few steps from the plan appear in the trace, or multiple extraneous actions occur. The structure or sequence of the plan is mostly lost.\n\n**0.0 \u2014 none**: The trace shows little or no resemblance to the plan. Steps are ignored, replaced, or executed in an entirely different order.\n\nYour response must be valid JSON only, with no other text or characters.";
/** Evaluates how efficiently the agent executed its steps. Score 0–3 returned in JSON. */
export declare const EXECUTION_EFFICIENCY_PROMPT = "You are a meticulous and analytical EXECUTION EFFICIENCY evaluator. Your job is to score how efficiently an AI agent executed its steps to accomplish a user task.\n\nYour assessment must strictly focus on the sequencing, resource utilization, and avoidance of redundant or wasteful actions within the execution itself, regardless of whether the task was ultimately successful or whether the plan was fully adhered to.\n\nHere is the data:\n    [BEGIN DATA]\n    ************\n    [User task]: {{ task }}\n    ************\n    [Execution trace (tool calls or agent calls)]: {{ trace }}\n    ************\n    [Agent output]: {{ agent_output }}\n    [END DATA]\n\nAssign a single integer score from 0 to 3 using the following criteria:\n\n**3 \u2014 Highly efficient**: All relevant actions are executed exactly once, in a streamlined and optimized sequence. There is no unnecessary busy work, repetition, backtracking, or wasted computation. Each step genuinely contributes to progressing toward the goal without extraneous operations. Error handling is appropriately lean and resolves quickly without requiring multiple attempts due to easily correctable input errors. Verification steps provide unique feedback, serve as sanity checks, or use a demonstrably different approach from the initial approach to ensure correctness, without duplicating prior effort.\n\n**2 \u2014 Mostly efficient**: Some minor instances of workflow inefficiency such as slightly redundant actions, non-ideal ordering of steps that cause minor rework, or missed opportunities for consolidation. There may be occasional minor input errors or misconfigurations that lead to a slightly increased number of attempts but are quickly corrected without major disruption. Inefficiencies have a noticeable but not significant impact.\n\n**1 \u2014 Somewhat inefficient**: Multiple instances of workflow inefficiency such as redundant actions, non-ideal ordering of steps that cause rework, excessive error handling, missed opportunities for consolidation, or unnecessary resource use. There may be input errors or misconfigurations that lead to several repeated attempts that could have been avoided.\n\n**0 \u2014 Highly inefficient**: Workflow is dominated by loops, duplicated efforts, poorly ordered sequence, or significant wasted computation that breaks progress. Multiple repeated tool or agent calls required to recover from preventable mistakes. Verification steps are highly redundant and provide no value. The workflow's operational flow is severely hampered by unnecessary or counterproductive actions.\n\nFor each step in the execution trace with an issue (e.g., redundancies, unnecessary retries, inefficient sequencing, missed optimization opportunities, or preventable errors), identify that step and explain the specific problem in your reason.\n\nRespond with a JSON object containing exactly two fields:\n- \"score\": an integer from 0 to 3\n- \"reason\": a concise explanation identifying specific issues or confirming efficiency\n\nYour response must be valid JSON only, with no other text or characters.";
/** Evaluates logical consistency of the plan and execution. Score 0–3 returned in JSON. */
export declare const REASONING_COHERENCE_PROMPT = "You are a meticulous and analytical LOGICAL CONSISTENCY evaluator. Your job is to score the logical consistency of an agentic system's plan and execution trace.\n\nYou must assign a single integer score from 0 to 3, where 0 is the lowest score according to the criteria and 3 is the highest possible score.\n\nHere is the data:\n    [BEGIN DATA]\n    ************\n    [User task]: {{ task }}\n    ************\n    [Plan]: {{ plan }}\n    ************\n    [Execution trace (tool calls or agent calls)]: {{ trace }}\n    ************\n    [Agent output]: {{ agent_output }}\n    [END DATA]\n\nScore the logical consistency of the trace, including both the plan and execution.\n\n**3 \u2014 Fully consistent**: Every action, claim, and transition in the trace is explicitly justified using information available in the prior context. Each statement is directly supported by and traceable to previous data, instructions, or content; no part of the response is fabricated or inferred from unstated assumptions. If an error from an earlier step is identified and corrected, the error is explicitly acknowledged before the correction is made, maintaining logical transparency. Each system instruction is followed. The reasoning remains coherent and free of contradictions or logical leaps.\n\n**2 \u2014 Mostly consistent**: There are occasional lapses in logic, minor unsupported assertions, or isolated explanatory gaps. Errors may be corrected, but corrections are occasionally introduced without clear acknowledgement of prior mistakes, creating minor inconsistencies or reducing transparency. Some statements may not be fully traceable to prior context, or some assumptions are made without explicit support from available evidence. Factual consistency may suffer from minor errors or embellishments, but the overall reasoning remains intact. Most previously assigned tasks and instructions remain intact.\n\n**1 \u2014 Somewhat inconsistent**: More frequent lapses in logic, unsupported assertions, or contradictions. Corrections are sometimes made without acknowledgement. Some actions or facts are not clearly grounded in the given information. The reasoning has noticeable gaps or invalid assumptions.\n\n**0 \u2014 Highly inconsistent**: There is frequent or severe breakdown in the logical flow; many statements are either unsupported by or cannot be grounded in the prior context. Corrections for earlier errors are often made without any explicit acknowledgement, resulting in contradictions or confusing transitions. Key actions or facts are invented, fabricated, or otherwise not observable in the given information. Major contradictions, invalid assumptions, or arbitrary transitions undermine the overall reasoning and conclusion. Most previously assigned tasks are not fulfilled, and internal system instructions are largely disregarded.\n\nBe critical in your evaluation. For each step in the trace with an issue (e.g., contradictions, unsupported statements, or previous instructions not followed), identify that step and explain the problem specifically. Flag any implicit assumptions.\n\nRespond with a JSON object containing exactly two fields:\n- \"score\": an integer from 0 to 3\n- \"reason\": a concise explanation identifying specific issues or confirming consistency\n\nYour response must be valid JSON only, with no other text or characters.";
/** Evaluates whether the agent's plan, execution, and output fulfilled the user's goal. */
export declare const GOAL_FULFILLMENT_PROMPT = "You are an evaluation assistant. Your job is to determine whether an AI agent has fulfilled the user's goal based on the plan (if any), the execution trace (tool/agent calls), and the final output.\n\nHere is the data:\n    [BEGIN DATA]\n    ************\n    [User goal]: {{ task }}\n    ************\n    [Plan]: {{ plan }}\n    ************\n    [Execution trace (tool calls or agent calls)]: {{ trace }}\n    ************\n    [Agent output]: {{ agent_output }}\n    [END DATA]\n\nEvaluate:\n1. Does the final output directly address and satisfy the user's original goal?\n2. If a plan was provided, is it logically connected to achieving that goal? Did the execution follow it?\n3. Do the tool/agent calls support progress toward the goal?\n4. Is the output accurate, complete, and useful relative to the goal?\n5. Are there any parts of the user's goal left unaddressed?\n\nRespond with a JSON object containing exactly two fields:\n- \"result\": one of \"fully_fulfilled\", \"partially_fulfilled\", or \"not_fulfilled\"\n- \"reason\": a brief explanation for your evaluation\n\n\"fully_fulfilled\" means the agent's output completely and accurately addresses the user's goal. The plan was sound and the output is a direct, useful answer.\n\n\"partially_fulfilled\" means the agent's output addresses some aspects of the user's goal but is incomplete, has minor inaccuracies, or leaves notable parts unaddressed.\n\n\"not_fulfilled\" means the agent's output fails to address the user's goal, is irrelevant, incorrect, or the plan was fundamentally flawed leading to an unhelpful result.\n\nYour response must be valid JSON only, with no other text or characters.";
/** Evaluates agent plan and execution against custom criteria (array of instructions). */
export declare const AGENT_CUSTOM_EVAL_PROMPT = "You are a meticulous AGENT BEHAVIOUR evaluator. Your job is to judge whether an AI agent's plan and execution conform to a set of custom evaluation criteria.\n\nHere is the data:\n    [BEGIN DATA]\n    ************\n    [User task]: {{ task }}\n    ************\n    [Plan]: {{ plan }}\n    ************\n    [Agent/tool definitions]: {{ definitions }}\n    ************\n    [Execution trace (agent/tool calls)]: {{ trace }}\n    ************\n    [Agent output]: {{ agent_output }}\n    ************\n    [Evaluation criteria]:\n    {{ criteria }}\n    [END DATA]\n\nEvaluate each criterion in order. For each criterion, decide whether the agent's plan and execution satisfy the criterion or violate it.\nIMPORTANT: The judgement should be based purely on the criteria itself, not generally on the agents plan and execution.\n\nAssign a single integer score from 0 to {{ max_score }} where:\n- {{ max_score }}: Every applicable criterion is fully satisfied with no violations.\n- Middle scores: Some criteria are satisfied; minor violations or gaps exist. Deduct one point per distinct criterion that is violated or only partially met.\n- 0: Most applicable criteria are violated or cannot be verified.\n\nFor every criterion that is violated or not satisfied, identify the specific step or element in the trace/plan responsible and explain the problem.\n\nRespond with a JSON object containing exactly two fields:\n- \"score\": an integer from 0 to {{ max_score }}\n- \"reason\": a concise explanation citing each violation or confirming compliance\n\nYour response must be valid JSON only, with no other text or characters.";
/** Evaluates whether the LLM selected the most appropriate tool(s) for the task. */
export declare const TOOL_SELECTION_QUALITY_PROMPT = "You are an impartial judge evaluating an LLM's tool-calling behavior, specifically whether the LLM selected the most appropriate tool or tools for the task.\n\nYour task: Determine whether the LLM's tool selection was correct or incorrect based on:\n- The conversation context (input)\n- The available tools\n- The LLM's output and tool invocation(s)\n\nCriteria:\nReturn \"correct\" only when ALL of the following are true:\n- The LLM chose the best available tool for the user query OR correctly avoided tools if none were needed.\n- The tool name exists in the available tools list.\n- The tool is allowed and safe to call.\n- The LLM selected the correct number of tools for the task.\n\nReturn \"incorrect\" if ANY of the following are true:\n- The LLM used a hallucinated or nonexistent tool.\n- The LLM selected a tool when none was needed.\n- The LLM did not use a tool when one was required.\n- The LLM chose a suboptimal or irrelevant tool.\n- The LLM selected an unsafe or not-permitted tool.\n- The tool name does not appear in the available tools list.\n\nBefore providing your final judgment, explain your reasoning and consider:\n- What does the input context require?\n- Can this be answered without tools, or is a tool necessary?\n- If a tool was selected, does it exist in the available tools?\n- Does the selected tool's description match the user's needs?\n- Is the selection safe and appropriate?\n- Is there a better tool available that should have been chosen instead?\n\nHere is the data:\n    [BEGIN DATA]\n    ************\n    [User task / input]: {{ input }}\n    ************\n    [Available tools]: {{ available_tools }}\n    ************\n    [Tool selection / invocations]: {{ tool_selection }}\n    [END DATA]\n\nRespond with a JSON object containing exactly two fields:\n- \"result\": either \"correct\" or \"incorrect\"\n- \"reason\": your reasoning and explanation\n\nYour response must be valid JSON only, with no other text or characters.";
export declare const SELECT_BEST_PROMPT: string;
//# sourceMappingURL=grading.d.ts.map