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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful behavior: results are ordered with in-progress tests first and finished tests newest-first. It also notes that this surface does not delete anything and that launch/stop require elevated access, though it does not detail result shape or pagination beyond the schema's limit/offset controls.

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 front-loaded with the core listing behavior and ordering, then adds useful context about siblings and access level. It is slightly longer than strictly necessary because it explains sibling actions, but every sentence remains relevant and no critical information is buried.

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 no output schema, the description appropriately explains that results are summary rows with stage information and ordered by in-progress versus finished status. It also points to sibling tools for deeper status and report views, though it does not enumerate the exact summary fields returned.

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 schema description coverage is 67%, with limit and offset already documented as page size and zero-based offset. The description implies project scoping and windowed pagination through 'a project's Load Tests' and 'a window of summary rows', but it does not add format or constraints beyond what the schema provides, leaving projectId only indirectly defined.

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 verb and resource (list a project's Load Tests) plus the ordering behavior: in-progress first with stage, then finished newest-first. It clearly distinguishes this listing tool from status-report and report-reading siblings.

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?

It explicitly routes the agent: use get_load_test_status to follow an in-progress test and get_load_test_report for a finished test's report. It also clarifies that launch/stop are separate actions requiring the Read+Write+Execute access level, so the agent knows when this tool is and is not the right one.

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