List Proxy Dial Accounts

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description does not need to restate that. It does add real behavioral context beyond the annotations: the tested fact that the wrong entry returns error 1003 and the correct entry is `pppoe_proxy`, which helps interpret failures. However it says nothing about result shape, pagination, or empty-list behavior.

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?

Very short and front-loaded: the purpose line comes first, followed by a brief empirical note. The purpose line largely restates the tool name/title, which is slightly redundant, but nothing else is wasted.

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 tool with an output schema and annotations, the requirements are minimal, and the description covers the endpoint quirk. What is missing is the one thing an agent actually needs for routing: how this differs from list_proxy_dial_online in the same family.

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 and the baseline of 4 applies. No parameter-related text is needed or expected here.

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 opening line gives a concrete verb+resource ("列出代拨账号" / list proxy dial accounts), so the agent knows exactly what it returns. It does not, however, distinguish this from the sibling list_proxy_dial_online (accounts vs. currently online sessions), which is the main ambiguity in this family.

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 statement of when to use this tool, when not to, or which sibling to prefer. The trailing note about the backend entry name (`pppoe_proxy` vs. `pppoe_proxy_user`) is an implementation/plumbing detail, not selection guidance for the agent.

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