pool_members

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

[READ] prefix indicates read-only nature. No annotations provided; description lacks details on idempotency, permissions, or side effects beyond the read hint.

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 concise with front-loaded read indicator. No unnecessary words, three lines cover purpose and args.

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, description is complete enough. No output schema, but return values are implied. Could mention error handling or default target 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?

Schema has 0% description coverage; description adds basic parameter info (poolid refers to pool_list, target from config). Adds some value but not comprehensive.

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?

Description explicitly states '[READ]' and lists resource types (VMs, CTs, storage). Clearly distinguishes from pool_list (list pools) and other list tools.

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?

Provides cross-reference to pool_list for pool id and mentions target as config value. Implicitly suggests use when you need pool members, but no explicit when-not or alternatives.

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