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

Adds three genuinely non-obvious behavioral facts beyond the annotations: do-not-disturb suppresses reminders but not unread counts, reading does not mark items read, and the result is a point-in-time snapshot rather than a live push stream. Note the tension with readOnlyHint=false — the description claims a pure read ('读取不会标记已读'), while the annotation says the tool is not read-only; since the annotation block appears to be a uniform all-false default set, this is not treated as a hard contradiction, but it is a residual ambiguity the description does not resolve.

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?

Three short sentences, no filler. The scope statement is front-loaded and each following sentence delivers one distinct caveat (DND semantics, non-marking read, snapshot vs. push).

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?

With an output schema present the return shape need not be described, and the description covers the remaining agent-critical unknowns: what is aggregated, that reads are side-effect-free, and that the data is a snapshot. Nothing required to call this zero-parameter tool correctly 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?

The tool takes zero parameters, so the schema imposes no semantics for the description to compensate for; baseline 4 applies. The description correctly implies the scope is fixed to the caller's own account ('本人'), which is the only 'parameter-like' constraint an agent needs to know.

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 concrete verb (读取/read) and enumerates exactly what resource it covers: unread summaries for private chats, group chats, invitations and group-event changes, plus notification settings. That scope is distinct from siblings such as fitmeet_messages_list or fitmeet_conversations_list, but no sibling is named, so the differentiation is inferred rather than stated.

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?

There is no explicit when-to-use or when-not-to-use statement and no alternative tool is named. Usage is only implied by the scope enumeration — an agent can infer this is the notification-overview entry point, but it must supply the routing logic itself.

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