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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description goes well beyond that by disclosing that unfinished tests return an error with status, and that advice buckets and detection flags are heuristics rather than diagnoses. It also instructs the agent to trust the underlying data over the buckets and to state contradictions, which is valuable behavioral context beyond any structured field.

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: the first sentence gives the core purpose and key output categories. The second and third sentences add important interpretation guidance. The final sentence is somewhat long and mixes post-invocation workflow guidance with tool usage, so it is not maximally concise, but every sentence contributes meaningful information.

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?

Given that an output schema exists, the description does not need to enumerate return fields. It covers error behavior for unfinished tests, the heuristic nature of advice buckets, and the prerequisite reading needed to use the result responsibly. Combined with the annotations and schema, nothing critical is missing for an agent to select and invoke this tool correctly.

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%: testId and errorUrlLimit are documented in the schema, but projectId is not described anywhere. The tool description does not add parameter-level meaning, though it does clarify the testId context by tying the report to finished tests. Since the description does not compensate for the undocumented projectId, this is adequate but not strong.

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 starts with a specific verb and resource: 'Get a finished Load Test's Test Report.' It then enumerates the concrete parts of that report (aggregate totals, error/advice picture, per-Population outcomes) and even defines behavior for unfinished tests. This is enough to distinguish it from the many sibling get_* tools without needing to name one.

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 clearly establishes that this tool is for finished load tests and that unfinished tests will respond with an error naming the status. It also gives explicit follow-up guidance to read get_documentation's 'analyzing-test-results' topic and cross-read the Scenario and Scripts before advising. It does not name a specific sibling alternative, but the resource is unique enough that this is not a significant gap.

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