list_dial_user_expiry_noticesLists expiry notices for dial-up users, helping you identify accounts nearing expiration and renew them before access is interrupted.
列出拨号用户过期通知
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description restates the name and adds nothing else—no scope, pagination, or filtering behavior beyond what the annotations and output schema convey.
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?
A single front-loaded verb-resource phrase with zero padding or repetition. It is efficient, though the extreme brevity means it carries little beyond the 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 and there are no parameters, so the return shape is documented elsewhere. Still, for an agent the description does not clarify what a 'dial user expiry notice' contains or how it relates to the adjacent expiry/notice listing tools.
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; there are no parameter semantics the description could usefully add.
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 (list) plus a scoped resource (dial user expiry notices), which is enough to separate it from the broader sibling list_expiry_notices. However, it offers no explicit sibling differentiation and the phrase is left in Chinese while all sibling names/descriptions are English, adding mild interpretive friction.
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?
No indication of when to call this versus list_expiry_notices, list_realtime_notices, or list_periodic_notices, and no prerequisites or context are given. The agent must infer usage purely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.