catalog_lineage

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

「查看」隐式表达这是一个只读查询行为，且描述补充了 asset_id 的来源以及资产外部的「源头文件→表/文档→工具」链路范围；但在无 annotation 的情况下，并没有进一步说明是否存在副作用、权限依赖、返回边界或失败行为，故只有中等透明度。

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?

对于只有一个必填 string 参数的工具，描述已覆盖用途、参数来源、使用场景，且有 output schema 兜底返回结构；但未提及血缘路径的格式、异常场景或权限上的前置条件，在无注解时稍显不够完整。

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?

schema 中 asset_id 没有任何描述，覆盖率 0%，而 description 明确说明「asset_id 必须来自 catalog_list_assets.items[i].asset_id」，为调用者补上了关键的取值来源语义；但没有给出格式示例或错误举例，离 5 分还差一点。

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?

描述以「查看某一资产从源文件到表/文档再到工具的链路」明确表达了具体动词、对象和遍历路径；与 catalog_list_assets 等兄弟工具的资产查看能力有明显区分，调用者无需打开 schema 即可知道这个工具专门负责血缘链路。

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?

「面试或排障时解释这份 Excel 怎么变成可查询指标」给出了明确的使用时机，但未说明何时不该用、也没有与 catalog_list_assets 等兄弟工具做条件对比，达不到 5 分要求的明确 when-not/alternatives。

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