kasko_lookup

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

注释已提供readOnlyHint（只读）和openWorldHint（结果可能变化）。描述在此基础上增加了关键行为：解析描述后匹配模型并按车辆返回价值；每个结果携带vehicle_code（保单上使用的品牌型号对）；当多个配置匹配时，要求代理呈现给用户而非猜测。这些行为准则超出了注释的覆盖范围，但未解释openWorldHint的具体含义（如结果集是否随时间变化）。

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?

描述仅用三个句子便涵盖了核心功能、使用定位（主工具）、返回值关键字段以及多匹配处理原则。每句承载明确信息，无冗余或无关内容，信息密度高且前端加载了最重要信息。

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?

针对4个参数（含2个必需）且有输出模式的场景，描述给出了基本完整的介绍：工具做什么、参数使用建议、返回值关键含义、以及用户交互策略。但缺少对无匹配或查询不精确时的处理说明，也未涉及与其他兄弟工具（如kasko_list_models）协作的典型流程。考虑到复杂度，描述已覆盖核心用例，留有少量改进空间。

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?

模式描述覆盖率为100%，基线为3。描述通过示例（“Include brand, nameplate and any trim or engine detail the user gave”）解释了如何填充query参数，并强调了brand可选以加速搜索。同时描述了返回值中的vehicle_code字段及其业务意义（保险公司要求的值），这为参数的使用提供了语义上下文，超过了模式本身的描述。

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?

描述以“Look up the kasko value of a vehicle from a free text description”开篇，明确动词（look up）和资源（kasko value），并指出输入是自由文本。后续强调这是“primary tool”，无需预先进行标识符查找，直接区隔于需要编码的兄弟工具（如kasko_get_value），使目的高度清晰且区分于同类工具。

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?

描述明确说“This is the primary tool”并给出使用时的行为准则（当多个配置匹配时呈现给用户而非猜测），暗示了这是首选入口。但未明确说明何时应转向其他工具（如kasko_list_brands或kasko_get_value），也缺少当自由文本无法解析时的回退建议，从而遗漏了明确的替代路径。

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