Submit training or knowledge data through dual compliance gates that flag sensitive content and block violations, with rejected entries recorded to the audit chain.
标准数据推送入口——企业存储按约定 schema 推送训练语料/知识数据，经分拣闸（敏感档标记）+ 合规闸（拦截违规）双闸入库，拒绝留痕进审计链。
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | 数据类型 | |
| source | Yes | 来源系统（审计可追溯） | |
| samples | Yes | 样本（训练语料行 / 知识片段） | |
| enterprise_id | Yes | 企业标识（租户隔离键） |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
在无注释的情况下，描述承担了行为披露的全部责任。它主动揭示了“分拣闸（敏感档标记）”和“合规闸（拦截违规）”的检查流程，以及“拒绝留痕进审计链”的副作用，这远超出标准行为描述，让智能体了解数据会被筛选并可能被拒绝且留下审计记录。虽然没有提及权限、异步性等，但已提供了关键行为特征。
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个必填、无嵌套、有枚举）且无输出模式，描述提供了目的和流程，虽未提及返回格式或错误处理，但根据模式已足够支撑调用。缺少返回信息和并发限制细节，但复杂度较低，描述基本完整，扣一分因未提及成功/失败的状态反馈。
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。描述中“按约定 schema 推送”仅对参数整体进行了暗示，但未具体说明每个参数（如kind、samples）的格式或约束，未在模式基础上增加实质语义。参数语义主要依赖模式本身。
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?
该描述用动词“推送”明确指出了操作，并明确资源是“训练语料/知识数据”，同时描述了“双闸入库”的流程，使其与兄弟工具（如搜索、调用、导出等）区分开来。它具体定义了工具是数据接送入口，而非通用操作。
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?
描述未提供任何“何时使用”、“何时不用”或替代工具的指导。虽然它明确定义了数据推送场景，但未说明与其他数据相关工具的区分条件或限制，例如哪些数据不适用此入口。这导致智能体无法明确判断是否应选择此工具而非其他。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.