cx_s_download_attachment

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

没有 annotations 提供只读/副作用信息，描述仅说明‘下载到本地’，未披露文件保存行为、是否覆盖、错误处理、权限要求或返回内容等关键行为特征。

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?

面对 2 个必填参数且 schema 无描述、无 annotations 的情况，描述只覆盖了部分语义，缺少 saveDir 和 objectId 的详细说明，也未提及输出行为，整体信息不足以支撑代理可靠调用。

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 描述覆盖率为 0%，描述中仅提到了 objectId 的定位作用，完全没有解释 saveDir 的含义、必需格式或与 objectId 的关系，无法帮助代理正确构造参数。

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?

描述明确说明了工具的作用：将作业/资料附件下载到本地，并指出定位方式为 objectId。虽然未与兄弟工具 cx_s_download_material 明确区分，但‘附件’这个措辞提供了一定区分度。

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?

没有提供任何使用场景说明，未说明何时应使用此工具而不是 cx_s_download_material 或其他下载类工具，也没有给出前置条件或注意事项。

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