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

readOnlyHint=true already establishes this is a safe read, yet the description adds genuinely new context: login/verified-phone precondition, the canFill field meaning 'can fill a blank slot', a non-empty-list guarantee, the phone number being withheld from the response, and a named error code. Only pagination/volume limits and full record shape are unstated, so it is strong but not exhaustive beyond 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?

There is no wasted prose, but the text is telegraphic: semicolon-separated fragments splice the precondition, the field semantics, three next-step tools, and a raw error code into one run-on block. The key matching rule is front-loaded, yet the error code and privacy note are buried mid-stream, hurting scannability.

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 zero-parameter read tool with a readOnlyHint and no output schema, this covers the essentials: what comes back at a broad level, the canFill flag, the no-phone error path, and the follow-up actions. The record structure and any pagination behavior remain undocumented, which is a modest gap given no output schema exists.

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?

The tool takes zero parameters, so the schema imposes no documentation burden and the baseline of 4 applies. The description instead explains output-side semantics (canFill) and the fieldKeys argument of the downstream claim tool, which is useful orientation but not parameter documentation for this call.

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 description states the resource and its matching rule: organization import records matched against the user's verified phone number, surfaced for claiming. It distinguishes itself from siblings by naming claim_organization_profile and dismiss_organization_claim as the follow-up actions, so an agent knows this is the read/list step of a claim workflow. It never uses an explicit verb like 'list' — the list nature is only implied via '非空列表' — which keeps it just short of a 5.

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?

Routing is explicit and complete: review each item, then call claim_organization_profile(fieldKeys) for items to keep, dismiss_organization_claim for items to drop, and get_signup_gaps as an optional follow-on. It also states the precondition (verified phone required) and the exact failure code organization_import_verified_phone_required when none exists. Both the when-to-use and the alternative branches are handed to the agent rather than inferred.

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