万忆跨域桥接

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

没有annotations，描述承担了主要行为披露责任；它说明了跨域桥接、BLOCK/CAUTION自动联动、按命中率列表、查看详情等行为，比完全沉默好。但未说明abstract沉淀模式是否有持久化副作用、bridge返回什么结构、get和list失败时的行为，行为透明度仍不完整。

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?

两句话覆盖了四个子操作和核心跨域迁移逻辑，信息密度高，动作列举紧凑，没有明显冗余。缺点是「护城河#3」和未解释的BLOCK/CAUTION术语占用了一定理解成本，但整体仍算精简。

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?

在无output schema、无annotations的情况下，描述覆盖了四个action的主要用途和参数约束，并暗示了部分返回行为（如list_patterns按命中率、get看详情）。但缺少对输出形状、limit如何应用、domain如何筛选、以及抽象模式后是否返回ID或确认信息等说明，对一个9参数的多模式工具来说只是刚好够用。

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?

input-schema对所有9个参数都有描述，且已经标注了abstract必填、bridge必填、get必填等条件，因此description无需重复基础语义。描述额外将参数组合归入四个action，便于快速理解调用姿势，但未补充limit作用范围、domain如何影响bridge结果等更深层语义，价值有限。

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?

描述明确说明工具的核心动作：把交易/写作/开发各领域的教训抽象成跨域底层模式，再进行跨域桥接，并能与兄弟工具如「万忆经验库」「万忆图谱搜索」区分开。但开头「护城河#3」和使用BLOCK/CAUTION这类内部术语，使整体表达不够口语化，且未直接对比任一兄弟工具，因此未到5分。

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?

描述按action列举了abstract、bridge、list_patterns、get各自的用途与参数组合，并提到BLOCK/CAUTION拦截时自动联动，提供了可执行的调用语境。但没有明确说明何时应优先使用本工具而非其他记忆工具，也没有给出when-not或替代工具的显式指引。

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