Lists WorkBuddy AI models available to the current account, showing chat, image, and video model IDs, capabilities, limits, and credit multipliers for use with wb_ai_chat.
列出 WorkBuddy AI（国际版）当前账号可用的全部模型。返回对话模型名单（含积分倍率、上下文窗口、推理档位、是否支持图片）以及图像/视频等非对话模型。模型 ID 可直接用于 wb_ai_chat 的 model 参数。
| Name | Required | Description | Default |
|---|---|---|---|
| refresh | No | 强制刷新目录（默认 5 分钟缓存），默认 false |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full disclosure burden. It helpfully enumerates what the response contains (credit multiplier, context window, reasoning tier, image support, plus image/video models), but does not state that this is a pure read with no side effects, nor mention caching/freshness behavior (that only appears in the schema's refresh description).
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 sentences, front-loaded with purpose, followed by return contents and downstream linkage. Slightly dense in the second sentence's metadata enumeration, but no wasted text.
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 no output schema, the description must convey returns and it does so thoroughly, and it ties the output to wb_ai_chat. It leaves wb_ai_status unaddressed and doesn't restate the read-only nature, minor gaps for a simple one-parameter list tool.
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?
Schema description coverage is 100% and the sole parameter (refresh) is fully documented in the schema, including the 5-minute cache default. The description adds no parameter detail beyond that, so the baseline 3 applies.
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 (列出) and resource (WorkBuddy AI 当前账号可用的全部模型), and even distinguishes its scope from the chat sibling by noting the returned model IDs feed wb_ai_chat's model parameter. An agent can identify this as the model-catalog tool without opening the schema.
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?
Implies usage by stating that returned model IDs can be passed to wb_ai_chat's model parameter, which routes the agent for downstream calls. However, there is no explicit 'call this before chatting' instruction, no exclusion against wb_ai_status, and no stated preconditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.