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 disclosure burden, yet it says nothing about runtime, side effects (test DB creation/teardown, fixture writes), expected duration, or failure semantics. Naming the command path is the only behavioral hint.

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 short, front-loaded sentence with no filler, but its brevity reflects under-specification rather than disciplined editing for a tool with four options and an output schema.

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?

The output schema covers return values, so those need not be described, but four undocumented parameters plus zero behavioral disclosure for a test-execution tool leaves the agent without enough to invoke it confidently.

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 0% and the description explains none of the four parameters. Ambiguous options like 'group' vs 'filter' (PHPUnit --group vs --filter), 'test_path' and the 'coverage' toggle receive no clarification anywhere.

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?

States a specific verb and resource ('Run the site's PHPUnit tests') and even names the underlying binary, which distinguishes it from test_run_kernel, test_run_behat and test_run_nightwatch by framework. It stops short of saying what distinguishes a PHPUnit run from the kernel-test runner beyond the name.

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?

No statement of when to prefer this over the sibling test runners or test_coverage_report, and no prerequisites (e.g. installed vendor dir, configured test database). The agent must infer usage 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.