add_transaction

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

没有 annotations，描述需承担行为披露责任。它揭示了严格一致性要求（evidence_name 完全一致）、金额需保留原文表述，以及逐笔而非汇总的登记方式。但未说明证据不存在时的错误行为、是否允许重复登记或追加、以及写入后的副作用，行为透明性仍有限。

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?

第一句直接点明用途，第二句强调核心业务规则，随后以紧凑的参数结构列出字段及必填要求。每句话都有实际价值，没有冗余内容，信息层级清晰，适合 agent 快速解析。

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?

在 0% 覆盖率且无 annotations 的情况下，描述覆盖了所有业务字段、必填性、与既有书证的关联，以及金额格式要求，整体足够支撑正确调用。不过 account、note、page 的语义仅靠字段名推测，缺少更明确解释，略微影响完整性。

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 对 args 内部字段覆盖率为 0%，描述以参数结构完整列出 evidence_name、date、payer、payee、amount、account、note、page 及必填性，并对 evidence_name 和 amount 提供额外语义约束（完全一致、保留原文表述）。这充分弥补了 schema 的空白。

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?

描述使用明确动词“逐笔登记资金流水”，限定资源为“已登记的书证”，并列举转账记录、回款、返利、工资提成等具体类型。这与 record_documentary_evidence、record_funds_summary 等兄弟工具形成清晰区分，用途明确且具体。

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?

描述明确说明银行流水类书证必须逐笔登记、不得只写汇总，划定了与汇总登记工具的使用边界；同时要求 evidence_name 与 record_documentary_evidence 登记的 name 完全一致，给出了前置条件。但未直接点名替代工具或明确“何时不要使用本工具”，因此未达满分。

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