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

Annotations only supply idempotentHint=true, so the description carries the burden and does it well: it declares the operation irreversible, mandates asking the user first, and names the specific error code surfaced for already-claimed records. Irreversibility plus idempotency are consistent (repeat calls are no-ops but the effect cannot be undone), so nothing contradicts the 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?

Very dense and front-loaded: purpose, meaning, irreversibility warning, workflow, and failure mode in three short clauses with no filler. The telegraphic fragments ('登录;' and arrow chains) trade some readability for compactness but every clause carries distinct information.

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 tool with no output schema, this covers everything needed to call it correctly: the concept behind the id, the irreversibility warning, the conversational precondition, the surrounding workflow, and the expected error case. No meaningful gap remains.

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?

With one parameter at 100% schema coverage, the schema already documents contactId as '待认领资料 id'. The description reinforces the domain concept (a pending claim record) but adds no format, sourcing, or lookup guidance beyond the schema, so the baseline of 3 applies.

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?

States a specific verb+resource ('把一条待认领资料标记为忽略') and immediately clarifies the semantic meaning ('不是我 / 不想被这个组织收录'), which distinguishes it from the sibling claim_organization_profile by naming that tool later in the text. An agent can tell exactly which of the many organization tools this is without opening a 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?

Gives an explicit ordered workflow: list_my_organization_claims → user says 'this isn't me' → this tool → claim the rest with claim_organization_profile, plus a login prerequisite. It also states the when-not condition (already-claimed records cannot be dismissed, returning organization_import_claim_unavailable). Nothing selection-relevant is left to inference.

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