Test Run Phpunit

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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not whether the run is read-only, whether it can write coverage artifacts or databases, how long it takes, or how results are surfaced. The only information conveyed is that tests execute, which the name already implies.

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?

It is a single front-loaded sentence with no wasted words, which is structurally fine. However, at this length the brevity is under-specification rather than true conciseness, since it omits information the agent needs.

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?

An output schema exists, so return values need not be explained, but for a 4-parameter tool with no annotations and no parameter documentation, the description is far too thin. It leaves usage context, side effects, and all argument semantics unaddressed.

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?

Four parameters (group, filter, coverage, test_path) have 0% schema description coverage and the description explains none of them. The meanings of 'group' vs 'filter' and the side effects of 'coverage' are left entirely to guesswork.

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 ('Run PHPUnit tests'), which is enough for an agent to know this executes the PHPUnit suite rather than Behat, Nightwatch, or Kernel tests. It stops short of explicitly contrasting with those sibling tools (test_run_behat, test_run_nightwatch, test_run_kernel), but the 'PHPUnit' qualifier does most of the differentiating work.

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?

There is no guidance on when to use this tool versus the other test runners, nor any prerequisites (composer install, Drupal bootstrap, working directory). The agent must infer everything from the name alone.

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