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

Annotations only declare readOnly=false, idempotent=true, destructive=false; the description adds the substantive semantics: graceful stop lets bots finish their current iteration and reports them in full, immediate kills mid-iteration, running tests move to STOPPING then end, unstarted tests are canceled, and already-ended tests are refused. That is a full state machine beyond what annotations convey.

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?

Front-loaded with the purpose and the graceful/immediate split, then guidance, then lifecycle. Every sentence carries information, though the state-transition sentence plus the follow-up-tool sentence makes it denser than strictly necessary for a three-parameter tool.

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?

No output schema exists, and the description compensates by telling the agent what the result carries (the post-stop stage) and which sibling to call next (get_load_test_status, then get_load_test_report). Combined with refusal and state-transition cases, nothing needed to invoke this correctly is 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 67% and the schema already documents 'immediate' and loadTestId. The description still adds real meaning to 'immediate' by explaining the mid-iteration cutoff and shortened final iterations, but projectId is not addressed in either schema or description, so not everything is covered.

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?

Opens with a specific verb+resource: 'Stop a Load Test,' and immediately contrasts it with launch_load_test / get_load_test_status by describing the stop lifecycle. An agent can tell exactly what this tool does without opening 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?

Explicitly states the default behavior and the decision rule: 'Stop gracefully unless the user asks to kill the test or the target needs relief now.' It also covers the edge case of killing an already-STOPPING test, giving both when-to and when-not guidance.

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