add_while_controller

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

With no annotations provided, the description carries full behavioral burden. It transparently explains that samplers repeat while the condition holds, and details the condition semantics: blank or 'LAST' loops on last sampler success, otherwise a JMeter expression re-evaluated until it evaluates to 'false'. This is substantial and useful.

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 sentences with zero fluff. It front-loads the primary action, then explains the condition logic efficiently. 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?

The description covers the core behavioral aspects: parent placement, looping behavior, and condition semantics. It omits return value details, but there is no output schema to contradict. It also does not mention potential error cases, but for a controller-adding tool this is acceptable. Overall it is fairly complete for an agent to call correctly.

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 0%, so the description must compensate for all parameters. It thoroughly explains the 'condition' parameter semantics, which is the most complex. However, it does not explicitly define planId, parentId, or name, though their meanings are somewhat inferable from the tool name and context. Given the 0% coverage, this is a partial compensation.

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 clearly states the tool adds a While Controller under a parent, with a specific verb and resource. It explains the controller's purpose but does not explicitly differentiate from sibling tools like add_loop_controller or add_if_controller, which could be ambiguous to an agent.

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?

It gives context that the parent is usually a Thread Group, which helps placement, but it does not explicitly state when to use this over alternatives like loop or if controllers. The looping semantics are described but not the decision criteria for choosing this tool.

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