Get Notifications

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

readOnlyHint=true already declares this as a safe read, and the description adds nothing beyond that: no scope (all notices vs unread vs recent), no ordering or pagination behavior, no indication of what the list contains. With annotations carrying the safety profile, the description contributes no additional behavioral 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?

It is a single short phrase with no waste, but this reflects under-specification rather than deliberate conciseness. Nothing is front-loaded because there is no second piece of information to order.

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?

An output schema exists, so return values need not be described, and with zero parameters the surface is small. Still, in a tool set crowded with notice/log/list siblings, the description leaves the most important question — which notification source this returns — unanswered.

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 there is nothing for the description to disambiguate; baseline 4 applies. Schema coverage is 100% by definition of an 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?

The description ("获取消息通知列表", get message notification list) is essentially a restatement of the tool name and title "Get Notifications". It gives no distinguishing detail against nearby siblings such as get_messages, get_warnings, list_realtime_notices, or get_notification_log, so an agent cannot tell which notice source this covers.

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 when-to-use guidance, no mention of alternatives, and no prerequisites or context. With four or five sibling tools that all return notices/logs/messages, the absence of routing guidance is a real gap; only the bare action is stated.

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