add_tcp_sampler

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

There are no annotations, so the description carries full responsibility. It states it opens a connection and sends data, which is basic behavior, but it omits critical details like connection lifecycle (close/reuse), timeouts, response handling, or side effects. An agent would be unaware of several configurable behaviors that affect execution.

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 a single, front-loaded sentence with zero filler. It efficiently conveys the core purpose without redundancy, making it easy to parse quickly.

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?

Given 12 parameters, no output schema, and no annotations, this description is far from complete. It fails to clarify connection management, timeout behavior, or what happens after sending data. An agent would need to guess at many operational aspects, making it insufficient for a complex sampler tool.

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 only 17% (only 'request' and 'classname' have descriptions). The description adds no parameter-specific explanations beyond the schema, failing to compensate for the low coverage. Parameters like noDelay, closeConnection, reUseConnection, and timeouts are left entirely to the agent's inference.

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 action (add a TCP Sampler), the resource (under a given parent, typically a Thread Group), and the specific behavior (opening a raw TCP connection and sending request data). This distinguishes it from HTTP, FTP, and other sampler siblings without needing to inspect the schema.

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 provides placement guidance (under a parent, usually a Thread Group) but gives no explicit when-to-use versus alternatives, no exclusions, and no mention of when not to use it. The purpose implies raw TCP usage, but the description does not actively route the agent away from other samplers.

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