remove_load_balancer_member

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

Annotations already mark destructiveHint=true. Description adds key behavioral detail: 'IRREVERSIBLE: the member stops receiving traffic immediately' and confirms the scope requirement. Sufficiently transparent beyond annotations.

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?

Four sentences, each essential: purpose, scope, irreversibility + confirmation, ID sources. No redundant or missing content. Front-loaded with action.

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 3-parameter destructive tool with no output schema, the description covers all necessary context: action, prerequisites, behavior, confirmation requirement, and data dependencies. No gaps.

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 coverage is 100% with brief descriptions. The description adds value by clarifying the origin of id and memberId, and elaborating on the confirm parameter's role. Enhances understanding beyond schema alone.

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?

Clear verb 'Remove' + specific resource 'member from a load balancer pool'. Distinguishes from sibling tools like add_load_balancer_member and delete_load_balancer.

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?

Explicitly states required scope (services:write), irreversibility, and the need for explicit user confirmation. Also specifies data sources for IDs. However, does not explicitly contrast with alternatives like 'delete_load_balancer'.

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