Generate, smoke-test, run, and summarize a load test in one call

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently lists the internal pipeline with arrows, showing the sequence and that it runs the full flow. It does not mention failure behavior, duration, or real load side effects, but the chain itself is clearly disclosed.

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: the first states the pipeline, the second gives alternative usage. It is front-loaded with the core purpose and every sentence earns its place with no filler.

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 the tool's complexity as a multi-step convenience wrapper, the description adequately explains the workflow and when to use granular tools instead. It does not describe the return value or failure semantics, and there is no output schema, but the pipeline names (e.g., get_test_metrics) and alternatives make it reasonably complete for an agent.

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?

The description adds no parameter-level information. The schema has a single `plan` parameter with 0% top-level schema description coverage, and the description does not compensate by explaining what the plan should contain or how it maps to the chained tools. The nested schema is helpful, but the description itself contributes nothing to parameter semantics.

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's purpose: it chains generate_k6_script -> smoke_test_script -> run_load_test -> get_test_metrics. The title also explicitly says 'Generate, smoke-test, run, and summarize a load test in one call,' and the description distinguishes it from its granular siblings by naming them and framing this as a convenience wrapper.

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?

The description explicitly says to use the granular tools instead when you want to inspect/adjust the script between steps, or re-run the same script with different load without regenerating it. This gives clear when-to-use and when-not-to-use guidance, making the alternative usage obvious.

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