Load test

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds genuinely useful context beyond that: request volume/rate ceilings, a 30-second wall clock, and that targets must be hosts 'this session may call'. The ownership warning is real safety context, though it does not say what side effects repeated real requests may cause on the target.

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?

Two sentences, front-loaded with the action and outputs, then constraints and safety. Tight overall; the constraints clause largely duplicates schema maximums, which is the one mild redundancy.

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?

An output schema exists so return shape need not be spelled out, and the description still previews the reported metrics. Combined with the safety and scope statements, an agent has enough to invoke it correctly; only the interaction between the rps/requests/duration caps is left to inference.

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 100% with per-parameter descriptions, so the schema carries the semantics. The description only restates the limits in prose ('Limited to 20 at once, 30 seconds and 5000 requests') without adding syntax or default-interaction detail beyond what the schema already documents.

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?

States a specific verb and resource ('Send one saved request many times at once') plus the reported outputs (throughput, latency percentiles, status codes, error samples). It implicitly contrasts with the single-send sibling send_request by emphasizing 'many times at once', but never names an alternative, so it stops short of full sibling differentiation.

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?

'Only test systems the developer owns' gives a prerequisite/eligibility rule, and the caps define operational bounds. However there is no explicit when-to-use guidance versus send_request or run_folder, and no statement of what to do when a test needs to exceed the 20/30s/5000 limits.

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