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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description still contributes auth context (【需要登录】) and a downstream effect (影响推荐排序/affects recommendation ranking) that the annotations do not convey. It stops short of describing the shape of the returned tags.

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?

Two compact sentences, front-loaded with the login prerequisite and the core purpose, followed by the disambiguation routing. Every clause earns its place with no repetition of the title.

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-only tool with no output schema, the description supplies the essential context: auth requirement, effect on recommendations, and sibling routing. Only the returned preference structure is unaddressed, which is minor here.

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. The description correctly implies a no-argument 'fetch my own' call by using 本人/我的 throughout, with nothing to document in the empty 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?

States a specific verb (读取/read) and resource (本人兴趣标签/my interest tags) and immediately distinguishes itself from look-alike siblings by name. An agent can tell it apart from get_notification_prefs and list_my_match_preferences without opening any 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?

Explicitly frames the use case ('改前读取' — read before modifying) and routes the agent to the correct alternative for each adjacent need: get_notification_prefs/set_notification_prefs for push, list_my_match_preferences/set_my_match_preference for icebreaker direction. Clear when-to-use and when-to-use-something-else.

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