perf_generate_load_test

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

There are no annotations, so the description carries the full burden of disclosing behavior. It only says a script is generated; it does not state whether the script is returned as text, written to a file, whether existing files are overwritten, or what output format to expect. For a generation tool without an output schema, this is a meaningful gap.

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?

A single sentence with no filler or repetition. It conveys the core purpose immediately and is easy to parse, though 'comprehensive' is slightly promotional rather than informative.

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?

With five parameters, no annotations, and no output schema, the one-sentence description is not sufficient for an agent to know what the tool returns or how to interpret the result. It does not cover behavior, output location, file handling, or typical usage flow, leaving significant context missing.

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 80%, so the baseline is 3. The description adds little beyond what the schema already provides, merely referencing application endpoints which maps to base_url and endpoints. The tool and scenario parameters, which affect the generated script, are not mentioned in the description.

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 states a specific action (generate) and resource (load test script) targeting application endpoints. It is clear enough to distinguish from unrelated siblings, though it does not explicitly differentiate itself from nearby tools like api_benchmark or e2e_generate_scenarios.

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?

No guidance is provided on when to use this tool versus alternatives such as api_benchmark, perf_analyze_bottlenecks, or test generation tools. The description implies usage for load testing but offers no exclusions, prerequisites, or selection criteria.

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