vsz_list_blocked_clients

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

No annotations are provided, so the description must fully disclose behavior. However, it only states the action 'List' and offers no details on authentication, pagination, output format, or potential side effects. The read-only nature is implied but not explicit, leaving significant gaps.

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 concise and front-loaded with the primary purpose. The Args section adds necessary parameter semantics without unnecessary fluff, making it efficient and easy to scan.

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 simple list tool with an output schema, the description covers the core purpose but lacks guidance on pagination, permissions, or related sibling tools. It is minimally sufficient but not comprehensive given the absence of annotations.

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?

With 0% schema coverage, the description adds meaning by specifying 'host' as the 'vSZ controller IP or hostname', which the schema's 'Host' field does not convey. This compensates for the schema gap, though it does not mention protocol or port requirements.

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 uses the specific verb 'List' and clearly identifies the resource as 'blocked (blacklisted) clients'. This distinguishes it from sibling tools like vsz_list_clients (all clients) and vsz_get_client (single client), so the purpose is unambiguous.

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 description implies the tool is used to view blocked clients, but it does not explicitly mention when to use it vs alternatives such as vsz_list_clients or vsz_query_clients. There is no exclusion criteria or alternative guidance provided.

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