list_lb_pools

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the '[READ]' tag merely restates them. The list of returned fields is real added context but is also covered by the output schema, and nothing is said about pagination, auth, or rate limits. With annotations carrying the safety profile, this is adequate but thin.

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?

Two short sentences, no filler: the read tag and resource are front-loaded, the return shape follows, and the sibling routing hint closes it. Every sentence earns its place.

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-required-param, read-only list tool with full schema coverage, an output schema and complete annotations, this is nearly sufficient. The only soft spot is that pool-related prerequisites (e.g. whether a Controller connection must exist) are left implicit, which is minor.

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 single vs_filter parameter is fully documented there (substring match, omit for all pools). The description adds no syntax or filtering nuance beyond the schema, 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+resource ('Discover pools on the Controller') and enumerates the returned fields (Name, member count, Enabled, short UUID). It also distinguishes itself from the sibling list_lb_pool_members by positioning itself as the prerequisite call, so an agent can tell the two apart without opening schemas.

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?

Gives explicit sequencing guidance ('Use this before list_lb_pool_members') plus the reason pools are often named differently from the VS that use them, which tells the agent when this tool is needed. It stops short of stating when *not* to use it or naming any alternative entry point.

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