test_run_suite

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

With no annotations, the description carries the full burden. It usefully discloses two behaviors — sequential execution and writing extracted values into active environment variables (a real side effect) — but says nothing about failure handling (does it abort on the first failed assertion?), whether extracted variables persist after the run, or permission/file-read implications.

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?

One dense, front-loaded sentence covering the full pipeline with no filler. The comma-separated capability list is efficient, though it reads as an inventory rather than prioritized guidance.

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 complex tool with no output schema, no annotations, four parameters and deeply nested step/assertion objects, the description omits data-driven mode, the report's contents, and failure semantics. An agent would have to infer too much about how errors in one step affect the rest of the suite.

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 description coverage is 75%, so the schema largely documents the parameters; the description only aligns with extractVariables ('extract dynamic fields to active environment variables'). It adds no guidance on steps structure, assertion semantics, or when dataSource/confirmFileAccess are needed beyond what the schema already states.

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?

A specific verb (execute) with a clear resource (multiple sequential REST requests) plus the additional behaviors — variable extraction, assertions, Markdown report. 'Multiple sequential' implicitly separates it from the single-request http_request sibling, but no sibling is named explicitly.

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?

Usage is implied by the name and the enumeration of capabilities (test-suite style execution), but the description never says when to pick this over http_request or suite_save/suite_load, nor does it state prerequisites such as an active environment or the confirmFileAccess requirement for dataSource.

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