list_voice_models

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that only slots that are imported and compatible with the engine are returned, which is useful scoping. Even so, it says nothing about ordering, whether empty results are possible, or how the slots relate to the pitch and index controls.

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?

The description is two short sentences and has no wasted text. It front-loads what the tool returns, then gives the action the agent should take next.

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?

The tool is simple, and an output schema exists, so the description does not need to enumerate the return values. What it covers (what the list contains and its intended downstream use) is enough to call the tool correctly. The only minor gap is the absence of stated ordering or emptiness behavior.

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 is no parameter behavior for the description to explain. The description correctly does not claim any input, and instead focuses on what the returned slots are for.

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 gives a specific verb and resource: it lists RVC model slots imported by the compatible engine, and it states the scope in a way that separates the tool from sibling list_local_models. It doesn't name the sibling, so an agent has to infer the difference from the 'RVC model slots' phrasing, but the purpose is nonetheless clear.

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?

The second sentence, “请用返回的槽位选择角色,” implies that the returned values are meant to feed a selection step, most likely select_voice_model. It never explicitly names the follow-up tool, nor does it state when to prefer this tool over list_local_models, leaving the routing implicit.

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