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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds beyond that: a login requirement, the fact that the payload contains private personal data (含本人私有资料), an explicit caution to confirm before external sharing (外发须确认), and a resource URI. That is meaningful operational context.

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?

Front-loaded with the login precondition, then the content list, then the combo chain and resource URI. Bracket labeling keeps it scannable and there is little filler. It is dense jargon (canOffer, 补卡) and slightly cramped, but every clause carries 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 parameterless read tool with no output schema, the description supplies the required login, the sensitivity warning, the returned field inventory, and the follow-up chains. An agent has enough to invoke it correctly and to handle the result responsibly; only sibling differentiation is thin.

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 baseline is 4 per the rubric. Although the description enumerates the card's fields, those are outputs rather than inputs, and there is no output schema to lean on, so the enumeration is a mild bonus rather than a parameter clarification.

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 (读 / read) and resource (完整本人名片) and enumerates what the card contains: canOffer, group link visibility, products, roles, followed products, and missing items (缺项). This lets an agent know exactly what data comes back. It does not, however, contrast itself against near-siblings such as get_my_profile or get_my_work, so differentiation is left implicit.

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 【需要登录】 marker gives a precondition and the 【组合链】 block names follow-up tools (update_my_profile/set_my_role_profile to fill gaps, list_needs_feed→contact_need→send_message), which implies usage context. However, it never says when to prefer this over get_my_profile/get_share_card_manifest, so alternative-selection guidance is missing.

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