删除一条线索
delete_broker_lead【需要登录】永久删除一条线索(只做单条,不开批量)。删了拿不回来,发起前把这条线索的名字念给用户确认。 【口径】已经带进来真人的线索(归因已落袋)删不了,服务端会拒——那是你分账账本上的一行。想清理请优先用 update_broker_lead(patch={archived:true})。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| leadId | Yes | 线索 id |
delete_broker_lead【需要登录】永久删除一条线索(只做单条,不开批量)。删了拿不回来,发起前把这条线索的名字念给用户确认。 【口径】已经带进来真人的线索(归因已落袋)删不了,服务端会拒——那是你分账账本上的一行。想清理请优先用 update_broker_lead(patch={archived:true})。
| Name | Required | Description | Default |
|---|---|---|---|
| leadId | Yes | 线索 id |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
虽然注解已声明destructiveHint=true和readOnlyHint=false,但描述补充了“需要登录”“永久删除”“删了拿不回来”“发起前确认”“归因已落袋删不了”等关键行为细节,这些超出了注解的范围,帮助代理正确执行并避免误操作。无矛盾。
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?
工具只有一个参数,无输出schema,描述涵盖了所有关键行为:需要登录、永久删除、不可恢复、需用户确认、限制条件(归因已落袋不可删)、替代方案(update_broker_lead归档)。对于代理正确调用和规避风险来说,信息已足够完整。
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?
只有一个参数leadId,schema描述为“线索 id”已覆盖100%,描述没有额外解释参数含义或格式。按照规则,schema覆盖率>80%时基线为3,描述未添加新信息,因此保持3分。
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?
描述明确说明了动词(永久删除)、资源(一条线索),并限定只做单条、不开批量,与兄弟工具update_broker_lead(用于更新/归档)形成鲜明区分。开头的“永久删除”直接点出核心动作,没有歧义。
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?
描述明确给出了何时使用(当需要永久删除时),并明确给出了替代方案:想清理请优先用update_broker_lead(patch={archived:true})。还说明了在“归因已落袋”的情况下服务端会拒绝,为用户提供了清晰的预期和排除条件。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.