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

Despite annotations already marking destructiveHint=true and readOnlyHint=false, the description adds material behavioral context: the operation is irreversible ('不可撤销'), requires user confirmation before calling, and fails for already-claimed records with organization_import_claim_unavailable. It also explains the login requirement and the semantic meaning of the ignore action.

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?

The description is compact and organized into labelled sections; the most critical warning (irreversible, ask user) is front-loaded with bold markers. Every sentence adds useful operational or semantic information, with no filler.

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?

For a single-parameter mutation with no output schema, the description covers prerequisites (login), policy constraints (ask user, irreversibility), workflow placement, and the known error condition. Nothing an agent needs to decide when and how to call this tool is missing.

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 coverage is 100% and contactId is already described as '待认领资料 id', so the schema carries the meaning. The description reinforces the connection to the pending-claim list but does not add new parameter-level details beyond the 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?

The first line states a specific verb ('标记为忽略') and resource ('待认领资料'), and defines the intent in parentheses ('不是我 / 不想被这个组织收录'). The combo chain explicitly contrasts it with claim_organization_profile, so an agent can distinguish ignore from claim without opening the 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?

The 【组合链】 section gives an explicit workflow: call list_my_organization_claims, wait for user confirmation, call this tool, then claim_organization_profile for remaining items. It also warns to ask the user first, and names the failing case 'already claimed' with its error code.

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