Dpanel Notice Unread

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

No annotations are provided, so the description carries full behavioral burden, and it discloses essentially nothing. It does not clarify whether this is a pure read or whether it also marks notices as read, what the response contains, or any pagination/volume characteristics — the 'unread' wording is genuinely ambiguous about side effects.

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 very short and not padded, but it is under-specified rather than concise: the parenthetical 'action=new' is cryptic internal jargon that most agents cannot interpret, and the phrase conveys no more information than the tool name.

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, but with no annotations, no parameter docs, and an ambiguous verb, the description should at minimum state whether this is a read-only retrieval and how it relates to dpanel_notice_list. It does neither.

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 explain; baseline 4 applies. The 'action=new' parenthetical adds a small amount of meaning about the underlying 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 restates the tool name ('未读通知' = unread notifications) and adds a terse API hint ('action=new'). It identifies the resource but does not clearly distinguish this from the sibling dpanel_notice_list, so an agent cannot tell from the description alone whether this filters unread items or retrieves a count/list.

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 and no mention of the obvious alternative dpanel_notice_list. The agent is left to infer the relationship between listing notices and listing unread notices.

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