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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds that this is a polling call sequenced after a run, but says nothing about whether intermediate results are partial, whether polling is rate-limited, or what states can be returned.

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 short sentences, front-loaded with the action and followed by the sequencing hint. No waste, though the second sentence is so terse it borders on under-specification rather than efficient concision.

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?

There is no output schema and no description of return shape, status values, or completion signal, so an agent polling this tool cannot tell from the definition when a run is finished. Combined with two undocumented optional parameters, the definition leaves real gaps for a polling 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 coverage is only 50%: include_artifacts and include_receipt_details have no descriptions anywhere, and the description does not explain what artifacts or receipt details mean or when to enable them. It only loosely gestures at "results," leaving half the parameters undocumented in both places.

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: checking status and results of a k6 test execution. It distinguishes itself from the upstream action by naming k6_run_test, but does not clarify its relationship to near-siblings like k6_report or get_execution, which plausibly also return run outcomes.

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?

"Poll this after k6_run_test" gives a clear prerequisite and implies repeated invocation, which is useful. However, there is no guidance on when to stop polling, no polling cadence, and no exclusion telling the agent when to prefer k6_report for the final results instead.

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