add_setup_thread_group

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

With no annotations, the description carries the behavioral burden. It discloses the key execution trait: the group runs once before all normal Thread Groups regardless of tree position. However, it does not explain call-level effects such as whether the test plan is mutated immediately, what happens on invalid parentId, or what response to expect.

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 no filler. It front-loads the core purpose and adds a typical use case and execution nuance, so every clause 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 is adequate for selecting the tool and understanding the special setUp Thread Group behavior. However, with 8 parameters, no output schema, and no annotations, it leaves the agent to infer parameter roles and error/return behavior, making it not fully self-sufficient for invocation.

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 only 38% and there are no annotations, so the description must compensate for undocumented parameters. It adds only the placement hint that the group is added under the TestPlan root, which partially informs parentId. It does not clarify required parameters such as planId, numThreads, or rampTimeSeconds.

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 names a specific verb and resource: 'Add a setUp Thread Group under the TestPlan root.' It clearly distinguishes this from a normal thread group by explaining the setUp thread group's special execution behavior, so an agent can tell it apart from add_thread_group.

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 a clear use case: 'typically used for one-time setup (e.g. login, seeding data).' It also clarifies that it runs before all normal Thread Groups, which helps an agent choose this tool over add_thread_group, though it does not explicitly mention the teardown sibling or say when not to use it.

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