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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description adds meaningful behavior beyond that: it returns only finished tests, orders newest first, returns summary rows in windows, and explicitly states that the surface does not launch, stop, or delete tests. This is consistent with the annotations and adds useful context.

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 action, then provides a concise domain definition and a pointer to the related report tool. Every sentence earns its place, and there is no redundant or filler content.

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?

For a read-only list operation, the description covers the key facts: what is listed, the ordering, the pagination style, the lifecycle context, and how to get more detail on a single test. The lack of an output schema is mitigated by the phrase 'summary rows,' and annotations cover the safety profile.

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 covers limit and offset with descriptions, but projectId has no description. The description implies projectId is the project identifier by saying 'a project's finished Load Tests,' but it does not add detailed parameter semantics. With 67% schema coverage, the description provides only marginal additional meaning.

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 uses a specific verb and resource: 'List a project's finished Load Tests, newest first, a window of summary rows at a time.' It clearly distinguishes itself from get_load_test_report by stating that reading one test's Test Report is a separate action, making the tool's purpose unambiguous.

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?

The description provides clear context: use this to list finished Load Tests and use get_load_test_report to read a single test's report. It also clarifies what this surface does not do (launch, stop, or delete tests), which helps avoid misuse, though it does not exhaustively enumerate all alternatives.

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